You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Matthew Beermann (JIRA)" <ji...@codehaus.org> on 2006/03/26 05:03:11 UTC

[jira] Updated: (MCLOVER-23) Allow custom license to be put in the repository

     [ http://jira.codehaus.org/browse/MCLOVER-23?page=all ]

Matthew Beermann updated MCLOVER-23:
------------------------------------

    Attachment: clover.patch.txt

> 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