Karl Heinz Marbaise created MASSEMBLY-690:
---------------------------------------------
Summary: Think about WARNING for
Key: MASSEMBLY-690
URL: https://jira.codehaus.org/browse/MASSEMBLY-690
Project: Maven Assembly Plugin
Issue Type: Improvement
Components: moduleSet
Affects Versions: 2.4
Reporter: Karl Heinz Marbaise
Priority: Minor
Currently the maven-assembly-plugin produces a WARNING like this:
{code}
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (make-bundles-attached) @ dist ---
[INFO] Reading assembly descriptor: proj1-assembly.xml
[WARNING] NOTE: Currently, inclusion of module dependencies may produce
unpredictable results if a version conflict occurs.
[INFO] Building zip:
/Users/kama/ws-git/apache/massembly/massembly-628/dist/target/dist-1.0.0-SNAPSHOT-bin.zip
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (make-bundles-not-attached) @ dist
---
[INFO] Reading assembly descriptor: proj1-dir.xml
[WARNING] NOTE: Currently, inclusion of module dependencies may produce
unpredictable results if a version conflict occurs.
[INFO] Copying files to
/Users/kama/ws-git/apache/massembly/massembly-628/dist/target/dist-1.0.0-SNAPSHOT-bin-dir
[INFO] ------------------------------------------------------------------------
{code}
If you use a moduleSet within your descriptor which should only happen if
really problem exist. In this
[case|https://github.com/khmarbaise/massembly/tree/master/massembly-628] it
does not exist really a problem, cause all versions are fine.
This means that we need to check the versions? Can we predict this in a better
way...? Is this really possible within maven-assembly-plugin ?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
