[mojo-dev] [jira] (MLICENSE-64) Please allow multiple additive licenseMerge elements

[jieryn (JIRA)]

jieryn created MLICENSE-64 Please allow multiple additive licenseMerge elements Issue Type: Improvement Assignee: Tony Chemit Created: 01/Jan/13 1:22 PM Description: On large projects which integrate many open source projects, there is a huge range of variation for even The Apache Software License v2.0, for example, we have: <licenseMerges> <licenseMerge>CDDL License|CDDL license</licenseMerge> <licenseMerge>Eclipse Public License, Version 1.0|Eclipse Public License - v 1.0|Eclipse Public License v1.0</licenseMerge> <licenseMerge>The Apache Software License, Version 2.0|Apache 2|Apache 2.0|Apache 2.0 License|Apache License|Apache License V2.0|Apache License Version 2.0|Apache License, Version 2.0|Apache Public License 2.0|Apache Software License 2.0</licenseMerge> </licenseMerges> Which causes grief for code formatting because of excessively long lines. If I attempt to have multiple licenseMerge statements with the same leading license name (aka the target license name), then license-m-p throws an error because I have two or more licenseMerge statements with the same target. Finally, it seems more intuitive to have a one for one mapping anyway. Please support this configuration mechanism. Project: Mojo's License Maven Plugin Priority: Minor Reporter: jieryn

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