Yeah - that's what I ended up doing for now, but you lose some of the Maven project goodness by doing that (auto SNAPSHOT build triggering, for one). I noticed, when I did it, that the Findbugs configuration moves from being a "Build Settings" config in a Maven project to a "Post-Build Action" in a freestyle one. My question here is, why as a Maven project build setting, it's not active during the mvn pre or post steps?
On Tuesday, 12 August 2014 05:09:24 UTC-5, Ullrich Hafner wrote: > > Did you try to use a freestyle project? > > Am Freitag, 8. August 2014 schrieb Eric Smalling : > >> I'm trying to find a workaround for >> https://issues.jenkins-ci.org/browse/JENKINS-22252?focusedCommentId=207405#comment-207405 >> >> I've found that using Maven 3.1.1 works but I don't want to lose some of >> the functionality in 3.2.1 so I'm trying to do my main build with 3.2.1 and >> then run findbugs:findbugs in a post-build Maven step. The findbugs plugin >> works and drops the xml file into target just fine but the Findbugs plugin >> doesn't seem to see it or even log anything about it. >> >> Does the plugin only activate during the main build step or is there some >> other trick to getting it to work with a post-build maven step? >> >> Thanks! >> Eric S. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
