[
https://jira.codehaus.org/browse/MFINDBUGS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288264#comment-288264
]
Jim McCaskey commented on MFINDBUGS-157:
----------------------------------------
Granted, but if I want the newer version of Findbugs which would go along with
this fix as well, then I would be out of luck. I'd have to upgrade Maven to
get a newer version of findbugs. Again I ask is that Findbugs place to force?
If it will work fine on 2.1.0 it seems somewhat arbitrary to force the upgrade
to 2.2.1. Why not say 3.0.3? All the intervening versions of 3.X have
problems as well (I'm not advocating that just stating it for illustrative
purposes)?
> 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
