Am 06/12/16 um 15:01 schrieb Robert Scholte: >> Hi, >> >> based on the feedback of the tests for current Maven 3.4.0-SNAPSHOT >> testing I have taken a deeper look into some of the changes. >> >> Based on the above issue we now have changed the behaviour of Maven >> 3.4.0 compared to 3.3.9 (and before). >> >> It looks like this change breaks some builds...
The changes are Aether bugfixes. That's not related to MNG-5227 in any way. The builds rely on misbehaviour and need to be fixed. >> >> So the question is: >> >> * Is this the correct path we are going? Yes. Fixing bugs is normal progress. >> >> Handling test scope in a more strict way than before? It's not a more strict way. It's an Aether bugfix making Maven behave as advertised. >> >> >> * I think we need to improve some of the docs to make it more clear >> and of course add this into the release notes with >> a red light in there... >> >> >> WDYT ? That will all go into the release notes, of course. There is more to come. Before we go any further. I've just pushed a MNG-6006 branch. Do this: Build a current Aether version from here: git clone https://git-wip-us.apache.org/repos/asf?p=maven-aether.git mvn install Then checkout the MNG-6006 branch and build a 3.4.0-SNAPSHOT with that Aether version. Use that 3.4.0-SNAPSHOT. We've allready progressed in fixing Aether bugs months ago. There currently is no way to make those bugfixes appear somewhere. With those bugfixes in place, you will discover various things to fail due to bugs in the poms of those failing projects. For example: Hervé Boutemy asked me to provide an IT for <https://issues.apache.org/jira/browse/MPLUGIN-296>. The answer to this is: Use a recent Maven version with those Aether bugfixes in place and see all existing ITs starting to fail. And it is correct those ITs are failing with the Aether bugfixes in place. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
