![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.4 |
|
Assignee:
|
Tony Chemit
|
|
Created:
|
17/Apr/13 9:26 AM
|
|
Description:
|
When using both the acceptPomPackaging option and the aggregate-add-third-party goal, this erases the aggregated result file.
The add-third-party goal should not run on the parent POM (the one on which the aggregate-add-third-party goal was run), or better: being run first then also aggregated with the children results.
If using acceptPomPackaging=true on my multi-module project, I get less than 10 third-party dependencies in target/generated-sources/license/THIRD-PARTY.txt.
If using acceptPomPackaging=false, I get 606 third-party dependencies but some are missing: those declared in POM type modules. I have to use that package type for the same reasons explained in MLICENSE-25: custom assemblies, ...
|
|
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
