wilx commented on issue #1231: URL: https://github.com/apache/maven-dependency-plugin/issues/1231#issuecomment-5158849945
This is caused by the duplicate `<plugin>` declarations and Maven's configuration merging, rather than by `maven-dependency-plugin`. Both blocks declare the same `groupId:artifactId`. Maven warns that the plugin declaration must be unique and merges the blocks. The first block's `<configuration>` is plugin-level configuration, so it acts as a default for every execution. When Maven combines it with the `unpack-help` execution configuration, the first `<artifactItem>` inherits the otherwise unspecified `<classifier>agent</classifier>` value. An `-X` run confirms that `agent` is already present in the final Mojo configuration before the dependency plugin executes. The POM should declare `maven-dependency-plugin` once, with one version, and put the Jolokia `<artifactItems>` configuration inside the `copy` execution. Each other execution should likewise contain its own `<artifactItems>` configuration. With that structure, the `unpack` artifact does not receive a classifier. There does not appear to be anything actionable in the plugin: it receives the configuration after Maven has already merged it and cannot determine which declaration supplied a value. I suggest closing this issue as a configuration problem rather than a plugin defect. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
