[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62104 ]
Matthew Beermann commented on MCLOVER-23: ----------------------------------------- That approach seems... unpleasant to me. You have to modify the root POM to make it work. What if each developer has different settings? They each must create their own build-tools.jar and install it into their local repo? Regardless, if this is going to be the recommended approach across a lot of projects, it might merit documentation up at http://maven.apache.org/guides/index.html... but that's a separate issue. > 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
