If you have a Maven-based module which bundles a JAR-packaging library in the same reactor tree, it would be desirable for it to use Class-Path: ext/mylib.jar rather than Class-Path: ext/some.group/mylib-1.0-SNAPSHOT.jar (when the JAR itself contains Maven metadata already).

relying on reactor is an unstable solution as the result will depend on what gets built together, eg. the results would differ for single module build and entire application build.

do the right thing without being told: if the JAR dependency has the same group ID and version as the module itself, use only the artifact ID in the copied filename.

that sounds like the way forward. Or maybe even for any -SNAPSHOT dependencies, no matter what the GAV is.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to