Le lundi 19 décembre 2016, 03:39:15 CET Christian Schulte a écrit : > Am 12/18/16 um 10:19 schrieb Hervé BOUTEMY: > You know what? We want also that libraries classpath are consistent > when built > > > and when used as dependencies: nothing specific to plugins and core > > extensions. Everything is built some time then used. > > If there are some unexpected discrepencies, we have an issue. > > That may well be! You can take > <https://issues.apache.org/jira/browse/MPLUGIN-296> as an example > demonstrating the difference. You just need a maven-plugin project to > build using the maven-plugin-plugin-3.4. Build that with Maven < 3.4 and > Maven >= 3.4 and compare the different plugin classpaths (-X). You'll > notice that in Maven 3.4 a provided direct dependency of the plugin is > collected and used to do conflict resolution and everything else and > then filtered out during resolving the artifacts. In Maven < 3.4 that > provided direct dependency is not collected and so another node (same > dependency but transitive) is used to do conflict resolution and > everything else which is then not filtered out during resolving the > artifacts. Maven 3.4 gets that right. from a purist point of view, I understand: from a user point of view, do you have any case where the new behaviour fixes a non-working configuration (instead of breaking a build that was working previously)?
> Maybe that's also the way > dependencies should be resolved as well. I must confess that what is the most suprising is that the resolution is different: IIUC, if the resolution was not different, the failure would have happened at build time, isn't it? Regards, Hervé > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
