[MASSEMBLY-690] Think about WARNING for module dependencies

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.4.1
• Component/s: moduleSet
• Assignee: Karl Heinz Marbaise
• Reporter: Karl Heinz Marbaise
• Created: 20/Mar/14 15:19
• Updated: 26/Jul/14 12:15
• Resolved: 25/Jul/14 14:12

Description

Currently the maven-assembly-plugin produces a WARNING like this:

[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] ------------------------------------------------------------------------

If you use a moduleSet within your descriptor which should only happen if really problem exist. In this case 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 ?