axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Sosnoski <>
Subject Re: [Axis2] 1.5 branch build broken
Date Mon, 28 Jun 2010 02:54:32 GMT
Andreas Veithen wrote:
> Dennis,
> I don't know any project that systematically tests its builds with all
> possible combinations of Maven version, Java version, Maven settings
> (e.g. maven.test.skip), platform (Windows, Linux, Mac OS X) and
> preconditions (local repository empty or not). We have Hudson jobs and
> these builds work fine. If people encounter problems in a specific
> environment or when running with non standard Maven settings, we
> expect them to report the issue and provide enough information to
> track down the issue.

I was running "mvn clean install" from a clean checkout of the branch, 
as I said in the original email about the missing Axiom jars. I'm 
running on Mandriva Linux 2009.1, using the Sun 1.6.0_10 JVM and Maven 

> For the jaxws-integration test issues, you simply complain but don't
> provide any relevant info about the issue. I'm tempted to say: as
> usual...  :-(
The big problem here is that the jaxws-integration test spews out dozens 
of stack traces and other verbose console output as part of the normal 
execution, so it's not at all clear to me what specific problem is 
causing the build to fail. The final output shows only one of the actual 
failed tests, which is:

Caused by: 


        ... 17 
AsyncClient.waitBlocking Exit, 29sec 
[SimpleHTTPServer] Stop 
Tests run: 10, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 16.381 
sec <<< 

[SimpleHTTPServer] Stop 

[SimpleHTTPServer] Stop 
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.024 
[SimpleHTTPServer] Stop called
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.172 sec

Results :

Failed tests:

Tests run: 318, Failures: 7, Errors: 0, Skipped: 0

[INFO] There are test failures.

> The jaxws-integration test issue has existed for quite some time in
> the trunk, but got fixed in a couple of days after it became clear
> that all the people who were complaining about this were actually
> trying to build with maven.test.skip=true (but forgot to mention
> this...).

I'm using "mvn clean install", as I said before. No other settings apply.

  - Dennis

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message