|
||||||||
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 |
- [mojo-dev] [jira] (MLICENSE-60) Provide mechani... Benson Margulies (JIRA)
- [mojo-dev] [jira] (MLICENSE-60) Provide me... Benson Margulies (JIRA)
- [mojo-dev] [jira] (MLICENSE-60) Provide me... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MLICENSE-60) Provide me... Benson Margulies (JIRA)
- [mojo-dev] [jira] (MLICENSE-60) Provide me... Benson Margulies (JIRA)
- [mojo-dev] [jira] (MLICENSE-60) Provide me... Christian Galsterer (JIRA)
- [mojo-dev] [jira] (MLICENSE-60) Provide me... Christian Galsterer (JIRA)
Currently for each artifact with a missing license either a local file (THIRD-PARTY.properties)or a dedicated artifact can be used. I'm looking for a way to have only one corporate wide file which contains the information for all "missing" license information.
In http://mojo.codehaus.org/license-maven-plugin/examples/example-thirdparty.html the following is stated.
Reading this, this looks like what I'm looking for, but unfortunately there is no more information how this is configured. In addition in http://jira.codehaus.org/browse/MLICENSE-60?focusedCommentId=317308&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-317308 is it said that there is better successor (therefore I'm commenting here), so I'm wondering if the quoted feature is the mentioned successor or not. If so some more examples how to configure it, would be highly appreciated. Can somebody provide an example?