Issue Type: Bug Bug
Affects Versions: 1.4
Assignee: Tony Chemit
Created: 17/Apr/13 8:59 AM
Description:

Hi,

As said in the documentation, the aggregate-add-third-party goal "Invokes the execution of this plugin's goal add-third-party prior to executing itself.".

The issue happens when there are dependencies between children. Let's say child2 depends on child1. Then the following issue is raised:

[ERROR] Failed to execute goal on project MLICENSE-JC-child2: Could not resolve dependencies for project org.codehaus.mojo.license.test:MLICENSE-JC-child2:jar:1.5-SNAPSHOT: Could not find artifact org.codehaus.mojo.license.test:MLICENSE-JC-child1:jar:1.5-SNAPSHOT in internal-snapshots (http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots) -> [Help 1]

A workaround is to build before: mvn clean install && mvn license:aggregate-add-third-party. But this prevents from automating the plugin execution during the build. This issue is much more annoying when releasing: I wanted the "release" profile to trigger the license plugin execution, optionally bundling the result file, ... Because of that bug, you simply can't bundle the third-party licenses on a release: building twice a non-SNAPSHOT artifact is not an option.

I don't know what would be the better fix but ideally, the aggregation should happen at the end of the build, or every module should aggregates itself its data to the common result file (like Jacoco plugin does for managing IT tests).
Being able to disable the fork could be a workaround for SNAPSHOT artifacts but won't work on releases.

Please find attached a sample IT case.

Project: Mojo's License Maven Plugin
Priority: Major Major
Reporter: Julien CARSIQUE
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