Which tests?? I don't even see failures with a clean repo. This build is
turning into a nightmare :)
On Tue, Apr 3, 2012 at 4:05 PM, Jason Porter <lightguard.jp(a)gmail.com>wrote:
I run -DskipTests on Fedora as well because of failing tests.
On Tue, Apr 3, 2012 at 14:04, Burr Sutter <bsutter(a)redhat.com> wrote:
> I have only tried building Forge about 5 times - putting the git clone
> results into a brand new directory.
>
> I had to use -DskipTests every time.
>
> Perhaps there is an environmental setting for the average Mac or Windows
> machine to allow for the tests to run.
>
> On Apr 3, 2012, at 3:55 PM, Lincoln Baxter, III wrote:
>
> Hey guys, have any of you seen an issue like this before?
>
> On Mon, Apr 2, 2012 at 6:07 PM, Burr Sutter <bsutter(a)redhat.com> wrote:
>
>>
>>
>> Begin forwarded message:
>>
>> *From: *Burr Sutter <bsutter(a)redhat.com>
>> *Subject: **forge build*
>> *Date: *March 31, 2012 2:26:33 PM EDT
>> *To: *Lincoln Baxter <lbaxter(a)redhat.com>, Koen Aers
<kaers(a)redhat.com>
>>
>> Please tell me how to make "mvn install" work with Forge.
>>
>> I use
>> "git clone
https://github.com/forge/core.git"
>> "mvn install"
>>
>> and I always have test failures on Mac & Windows
>>
>> Tests in error:
>>
>> testRunScriptNotHostHttpUrl(org.jboss.forge.shell.test.plugins.builtin.RunUrlP
>> luginTest): Unexpected exception,
>> expected<java.net.UnknownHostException> but wa
>> s<org.mvel2.CompileException>
>>
>> Tests run: 136, Failures: 0, Errors: 1, Skipped: 5
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Forge - Parent .................................... SUCCESS
>> [0.733s]
>> [INFO] Forge - Targeted Event Bus ........................ SUCCESS
>> [40.622s]
>> [INFO] Forge - Parser/Java API ........................... SUCCESS
>> [1.246s]
>> [INFO] Forge - Parser/XML ................................ SUCCESS
>> [0.950s]
>> [INFO] Forge - Shell API ................................. SUCCESS
>> [10.231s]
>> [INFO] Forge - Maven Integration APIs .................... SUCCESS
>> [22.668s]
>> [INFO] Forge - Git Integration ........................... SUCCESS
>> [7.097s]
>> [INFO] Forge - Test Harness .............................. SUCCESS
>> [1.277s]
>> [INFO] Forge - Maven Project Model ....................... SUCCESS
>> [18.364s]
>> [INFO] Forge - Parser/Java ............................... SUCCESS
>> [28.347s]
>> [INFO] Forge - Shell ..................................... FAILURE
>> [3:42.427s]
>> [INFO] Forge - Git Integration Tests ..................... SKIPPED
>> [INFO] Forge - Project Model Maven Tests ................. SKIPPED
>> [INFO] Forge - Test Harness (Web) ........................ SKIPPED
>> [INFO] Forge - Java EE APIs .............................. SKIPPED
>> [INFO] Forge - Java EE Integration Impl & Plugins ........ SKIPPED
>> [INFO] Forge - Scaffolding APIs .......................... SKIPPED
>> [INFO] Forge - Scaffolding Plugins ....................... SKIPPED
>> [INFO] Forge - Dev Plugins ............................... SKIPPED
>> [INFO] Forge - Scaffold Provider for Java Server Faces ... SKIPPED
>> [INFO] Forge - Modular Plugin Loader ..................... SKIPPED
>> [INFO] JBoss Forge - Distribution Build .................. SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 5:56.660s
>> [INFO] Finished at: Sat Mar 31 13:07:19 EDT 2012
>> [INFO] Final Memory: 30M/102M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.
>> 12:test (default-test) on project forge-shell: There are test failures.
>> [ERROR]
>> [ERROR] Please refer to D:\code\forge\core\shell\target\surefire-reports
>> for the
>> individual test results.
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e swit
>> ch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please rea
>> d the following articles:
>> [ERROR] [Help 1]
>>
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
>> eption
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>>
>> [ERROR] mvn <goals> -rf :forge-shell
>> D:\code\forge\core>
>>
>>
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>
>
> --
> Lincoln Baxter, III
>
http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at:
keyserver.net,
pgp.mit.edu
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev