[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62076 ]
Matthew Beermann commented on MCLOVER-23: ----------------------------------------- The thing is, the manufacturer of Clover specifies a particular algorithm that will be used to locate the Clover license, and I think we should strive for parity with that. Check the bottom of the page at: http://www.cenqua.com/clover/doc/ > Allow custom license to be put in the repository > ------------------------------------------------ > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Attachments: clover.patch.txt > > > It would be nice to share a custom license between different project. A > solution is to create a new artifact type and put the license in the > local/remote repositories and specify it using a dependency as any other > artifact. Idea suggested by Matthew Beermann. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
