Hervé,
The following IT fails after your changes:
Tests run: 732, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 450.697 sec
<<< FAILURE!
testit0064(org.apache.maven.it.MavenIT0064MojoConfigViaSettersTest) Time
elapsed: 0.547 sec <<< FAILURE!
junit.framework.AssertionFailedError: Expected file was not found:
/Users/jvanzyl/js/tesla/maven-integration-testing/core-it-suite/target/test-classes/it0064/target/fooValue
at junit.framework.Assert.fail(Assert.java:47)
at org.apache.maven.it.Verifier.assertFilePresent(Verifier.java:1014)
at
org.apache.maven.it.MavenIT0064MojoConfigViaSettersTest.testit0064(MavenIT0064MojoConfigViaSettersTest.java:51)
Do you get the same?
Why did you change so many plugins in the ITs? They are supposed the be a
(mostly) immutable set of tests and not a body of code that should be updated
just because there are new versions. They should remain constant over time,
which they have been up until now.
I don't think it's particularly useful and when we get a failure like this now
it's really hard to tell, with multiple points of variation, whether it's a
change in Maven itself or a change in the ITs
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
