[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62079 ]
Vincent Massol commented on MCLOVER-23: --------------------------------------- Hi Matthew, Your patch is not quite correct. You're not allowed to put any file in your local repository. This is an area reserved by Maven2 (it was open in Maven1). You have to go through Maven2 to put a file there. Thus the only solution to put a file there is to define a new artifact type. The other reason is that if you're working within a team you'll want to upload this file to your remote repository. Hi John, Yes you're right: using the same mechanism is the best solution. This allows putting the license file in a shared JAR. Better and more consistent than what I was proposing. > 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
