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

Posted to issues@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2006/03/27 18:53:44 UTC

[jira] Updated: (MCLOVER-23) Allow custom license to be passed as JAR resource, URL or File

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

Vincent Massol updated MCLOVER-23:
----------------------------------

    Description: In the same way it's done in the checkstyle and PMD plugins.  (was: 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.
)
    Fix Version: 2.1
        Summary: Allow custom license to be passed as JAR resource, URL or File  (was: Allow custom license to be put in the repository)

> Allow custom license to be passed as JAR resource, URL or File
> --------------------------------------------------------------
>
>          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
>     Assignee: Vincent Massol
>      Fix For: 2.1
>  Attachments: clover-license-fix.patch, clover.patch.txt
>
>
> In the same way it's done in the checkstyle and PMD plugins.

-- 
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