Hi Karl Heinz,
could you test current trunk version?
I hope http://svn.apache.org/r1667876 fixed the issue.
The other interesting part is: is seems like on (your) Mac the M2_HOME
isn't set by the mvn script, but for Windows it is...
thanks,
Robert
Op Thu, 19 Mar 2015 21:08:09 +0100 schreef Karl Heinz Marbaise
<khmarba...@gmx.de>:
Hi Robert,
> Hi Karl Heinz,
I think it has to do with the chain of Maven invocations, although it
shouldn't matter.
Just for me: how do you execute these tests? Plain old commandline or
buildserver or ...?
Just plain old commandline ;-)...
mvn clean verify ...
nothing odd....
Kind regards
Karl Heinz Marbaise
thanks,
Robert
Op Thu, 19 Mar 2015 07:12:33 +0100 schreef Karl Heinz Marbaise
<khmarba...@gmx.de>:
Hi Robert,
a followup...checked with Maven 3.2.5 as well and got the same
issue...so it seemed to be not limited to Maven 3.3.1...
Kind regards
Karl Heinz Marbaise
On 3/19/15 7:03 AM, Karl Heinz Marbaise wrote:
Hi Robert,
I have checked with Maven 3.3.1 on Mac and got the following:
Running org.apache.maven.shared.invoker.DefaultInvokerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.914
sec - in org.apache.maven.shared.invoker.DefaultInvokerTest
Running org.apache.maven.shared.invoker.MavenCommandLineBuilderTest
Tests run: 52, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.078
sec <<< FAILURE! - in
org.apache.maven.shared.invoker.MavenCommandLineBuilderTest
testShouldSetEnvVar_M2_HOME(org.apache.maven.shared.invoker.MavenCommandLineBuilderTest)
Time elapsed: 0.018 sec <<< ERROR!
org.junit.internal.AssumptionViolatedException: got: <[null]>,
expected:
every item is not null
at org.junit.Assume.assumeThat(Assume.java:95)
at org.junit.Assume.assumeNotNull(Assume.java:73)
at
org.apache.maven.shared.invoker.MavenCommandLineBuilderTest.testShouldSetEnvVar_M2_HOME(MavenCommandLineBuilderTest.java:1108)
Running org.apache.maven.shared.invoker.SystemOutHandlerTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
-
in org.apache.maven.shared.invoker.SystemOutHandlerTest
Running org.apache.maven.shared.invoker.SystemOutLoggerTest
Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002
sec - in org.apache.maven.shared.invoker.SystemOutLoggerTest
Results :
Tests in error:
MavenCommandLineBuilderTest.testShouldSetEnvVar_M2_HOME:1108 ยป
AssumptionViolated
Tests run: 92, Failures: 0, Errors: 1, Skipped: 0
Do i need to do something special to get those tests workig ?
Kind regards
Karl Heinz Marbaise
On 3/18/15 11:52 PM, Robert Scholte wrote:
Hi,
this release contains a critical fix for Windows users who want to
invoke Apache Maven 3.3.1. Due to
http://jira.codehaus.org/browse/MNG-5776 the start-script has been
renamed from mvn.bat to mvn.cmd, which caused that the Invoker
couldn't
find the executable file anymore.
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=18970
There are still 2 issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1&component=13271
Staging repo:
https://repository.apache.org/content/repositories/maven-1154
https://repository.apache.org/content/repositories/maven-1154/org/apache/maven/shared/maven-invoker/2.2/maven-invoker-2.2-source-release.zip
Source release checksum(s):
maven-invoker-2.2-source-release.zip sha1:
56fb87afb12378ebbf5ddf1546ac10528e18dca6
Staging site:
http://maven.apache.org/shared-archives/maven-invoker-LATEST/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
