[mojo-dev] [jira] (MFINDBUGS-205) Wrong dependency scope

[Sergei Ivanov (JIRA)]

Title: Message Title

Sergei Ivanov commented on an issue   Re: Wrong dependency scope Interestingly, only yesterday I ran into the very same problem with one of our custom plugins (only in our case we needed runtime dependencies, while the plugin's resolution scope was set up as 'compile'). It took me a couple of hours of testing and debugging before I discovered the root cause. This looks like a major change in behaviour in Maven 3.x, which has never been properly documented. Someone should raise it against the core team to update the documentation of the Project class (there's almost no javadocs at all in there). Also, a bunch of methods like getRuntimeArtifacts() are now marked as @Deprecated, but there is no documentation on what should be used instead. Add Comment   Mojo's FindBugs Maven Plugin / MFINDBUGS-205 Wrong dependency scope Hello, as we're using findbugs directly in eclipse, to prevent bugs being committed and additionally in our build environment (maven) to check the code frequently, we are focused, that both environments reporting the same issues. Unfortunately one of our developers found a difference - eclipse was reporting 43 bugs in the test (!) code, the build (mave... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email