[mojo-dev] [jira] (MLICENSE-28) aggregate-add-third-party should be able to use a THIRD-PARTY.properties for the aggreated licences

[Tony Chemit (JIRA)]

Tony Chemit commented on MLICENSE-28 aggregate-add-third-party should be able to use a THIRD-PARTY.properties for the aggreated licences I just creates a IT to verify what's existing at the moment for aggregate mojo and it works fine to me : the aggregate THIRD-PARTY.txt is created using "missing file" (src/license/THIRD-PARTY.properties) from his child. I will then not fix this issue (since it works). For others demands, I am not against them But it will be more clear to create an issue for each one. For the auto-filling of missing file, it is already using the deployMissingFile and useRepositoryMissingFiles property (but not working for aggregate goal and won't), but this is default configuration so you should have it. It will deploy for each of your artifact the missing file in the maven repository, so other maven project using a such dependencies will download the missing from the maven repository and use it). In other words, if you fill a missing license in a child 1, and child 2 uses child 1 then it will be filled for you stuff from the child 1 missing file; but if child 2 use same bad dependency than child 1 but does not depend on child 1 you are lost (for the moment). perharps could we introduce the feature to be able to use more than one missingfile or reacted modules, but not sure it is natural (and perharps complex). Any way hope I am clear (). If you need more information, feel free to ask.

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