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. Maybe that's also the way dependencies should be resolved as well. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
