[
http://jira.codehaus.org/browse/MFINDBUGS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Liljenberg updated MFINDBUGS-87:
--------------------------------------
Attachment: findbugs.patch
First try for a patch....not a Groovy developer myself so there are probably
plenty of room for improvements.
Will apply this patch and try it tomorrow :)
> Improve pluginList to support "mavenish" urls
> ---------------------------------------------
>
> Key: MFINDBUGS-87
> URL: http://jira.codehaus.org/browse/MFINDBUGS-87
> Project: Maven 2.x FindBugs Plugin
> Issue Type: Improvement
> Environment: All
> Reporter: Peter Liljenberg
> Assignee: Garvin LeClaire
> Priority: Minor
> Attachments: findbugs.patch
>
>
> If I want to add my own checkers to Findbugs I'm supposed to use the
> <pluginList> tag to provide the name (and path) to my jar file.
> This doesn't seem like a very "mavenish" way of resolving dependencies?
> Wouldn't it be better to supply a list of artifacts instead? And download
> whatever was necessary from repositories?
> Resolving and downloading artifiacts is easy to do and then the necessary
> filepaths (in your plugin code) can be resolved to the local repository.
> Would be nice to get this working since hardcoding a path is not really a
> feasibly solution for our team.
> <pluginList>group:artifact:version,group1:artifact:version</pluginList>
> could be used and then parsed in the code to a valid Artifact to be resolved.
> I'm not doing any Groovy work myself, but I could write the Java code
> necessary to get this to work and send it to you for conversion if you like?
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
