[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_61979 ]
John Allen commented on MCLOVER-23: ----------------------------------- I completely agree with the principal but think the approach adopted by checkstyle and PMD for custom resource resolution should be adopted:- A resource (in this case the license file) is specified by a URL which is resolved in a fallback manner covering HTTP, file and classloaders locations. This allows us to simply specify the license file as a file path and include a JAR depdency which contains that file path to the plugin using the standard maven dependency mechanism, the plugin will then locate the resource in the dependency jar. See checkstyle and PMD for details of this custom resource loader (if memory serves me right its a very simple helper method) > 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
