[
http://jira.codehaus.org/browse/MFINDBUGS-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265695#action_265695
]
Geoff Bennett commented on MFINDBUGS-141:
-----------------------------------------
Hi Garvin, thanks for the suggestion but the results and config that I have
shown above are for a 'root' module of a multi-module project, so effectively
it has been run as a single module project, so there is no need to skip
anything as I have only run it against one module.
As for the latest version of the plugin, I could not find the latest version in
a public maven repository anywhere. Is there a repo that I do not know about or
should I just download it from the plugin website and put it on our own repo?
> Make dependency resolution scope requirements the same as the compile plugin
> ----------------------------------------------------------------------------
>
> Key: MFINDBUGS-141
> URL: http://jira.codehaus.org/browse/MFINDBUGS-141
> Project: Maven 2.x FindBugs Plugin
> Issue Type: Task
> Reporter: Geoff Bennett
> Assignee: Garvin LeClaire
> Priority: Minor
>
> I have a multi-module J2EE configuration that has a lot of dependencies of
> scope 'provided'. Because they are not of scope 'compile' I cannot run
> findbugs.
> Shouldn't the findbugs plugin operate the same way that the compile plugin
> works with respect to dependencies? If this was the case, 'provided' would
> also be on the classpath.
--
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
