[
https://jira.codehaus.org/browse/MFINDBUGS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296150#comment-296150
]
Garvin LeClaire commented on MFINDBUGS-161:
-------------------------------------------
Do you have a sample with this error?
> Add option for dependency scope
> -------------------------------
>
> Key: MFINDBUGS-161
> URL: https://jira.codehaus.org/browse/MFINDBUGS-161
> Project: Maven 2.x FindBugs Plugin
> Issue Type: Improvement
> Affects Versions: 2.4.0
> Reporter: Terje Strand
> Assignee: Garvin LeClaire
>
> Currently we are enabling Findbugs on JUnit code using
> <includeTests>true</includeTests>.
> However, we then get a lot of warnings about missing classes:
> ----
> The following classes needed for analysis were missing:
> org.mockito.stubbing.Answer
> org.junit.Assert
> org.junit.Test
> org.mockito.stubbing.OngoingStubbing
> org.mockito.invocation.InvocationOnMock
> org.mockito.Matchers
> org.mockito.Mockito
> ----
> If I am not mistaken, I believe this is because FindBugs is analysing the
> test code using the "compile" classpath scope.
> Therefore, would it be possible to add an option, like the maven exec plugin,
> where one can chose which classpath scope to use?
> Thanks!
--
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
