[ 
https://jira.codehaus.org/browse/MFINDBUGS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288258#comment-288258
 ] 

Jim McCaskey commented on MFINDBUGS-157:
----------------------------------------

Is that really FindBugs job to enforce a version of Maven?  We use 2.1.0 and 
have been for some time with no trouble.  Since we have a version of Maven that 
meets the requirements for the plugin, why should we be forced to upgrade Maven 
in general?  Ultimately we have plans to upgrade our systems to Maven 3.0.X, 
but we might not have time for that.  We would like to get the benefit of 
MFINDBUGS-158 though without having to rock the whole cart.
                
> Update minimum requirement to Maven 2.2.1 for better Doxia Compatibility
> ------------------------------------------------------------------------
>
>                 Key: MFINDBUGS-157
>                 URL: https://jira.codehaus.org/browse/MFINDBUGS-157
>             Project: Maven 2.x FindBugs Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.3
>            Reporter: Garvin LeClaire
>            Assignee: Garvin LeClaire
>             Fix For: 2.4.0
>
>
> All Maven 2 versions come with a bundled Doxia version. This means that
> it is locked and cannot use newer versions of Doxia. Most current
> reporting plugins use Doxia 1.1.x which was introduced in Maven 2.1.0.
> Maven version prior to that cannot use Doxia 1.1 features like Doxia
> Logging.
> So when a reporting plugin using Doxia 1.1 is invoked by Maven 2.0.x
> there is a high probability that it will crash, in a way similar to what
> is described in the above issue.
> To remedy this I propose that all plugins that use Doxia 1.1+ has its
> Maven prerequisite set to 2.2.1.
> Why not 2.1.0 or 2.2.0 you may ask? Well, we don't want people to use
> them because Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and
> checksums respectively.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.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


Reply via email to