[jira] Created: (MFINDBUGS-87) Improve pluginList to support "mavenish" urls

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


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

     [ http://jira.codehaus.org/browse/MFINDBUGS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Garvin LeClaire reassigned MFINDBUGS-87:
----------------------------------------

    Assignee: Garvin LeClaire

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

     [ http://jira.codehaus.org/browse/MFINDBUGS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Garvin LeClaire updated MFINDBUGS-87:
-------------------------------------

    Priority: Minor  (was: Major)

I think this will be a similar situations as [MFINDBUGS-81|http://jira.codehaus.org/browse/MFINDBUGS-81]

I have pared the dependencies down to the appropriate versions that work with the dependency resolvers (I hope), so this function can be added to the plugin list option.

I will keep the format for declaring the dependency the same.  This will allow FindBugs users with little Maven experience to be productive immediately.  The plugins can still be deployed as a Maven artifacts while letting the user pick a subset of the artifact's FindBugs plugins.

With the release of Findbugs 1.3.9 this may be defered to the next release.

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

    [ http://jira.codehaus.org/browse/MFINDBUGS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196073#action_196073 ]

Peter Liljenberg commented on MFINDBUGS-87:
-------------------------------------------

Any chance that this will be fixed any time soon?

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

    [ http://jira.codehaus.org/browse/MFINDBUGS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196810#action_196810 ]

Garvin LeClaire commented on MFINDBUGS-87:
------------------------------------------

This is something for a future release.  I am going to clean up a few loose end and get a release out this week.

Garvin

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

     [ 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