> This means two different people would use different versions of findbugs for > the same project, if one happens run the build using java 6 and the other > java 7. I don't think this is a good idea.
It does sound somewhat dangerous but I'm wondering what's the practical issue with this. It would be cool if our findbugs plugin worked out of the box for java6 people, too. Perhaps a lifecycle message saying that we're using downgraded version of Findbugs is enough. OTOH, java6 is no longer supported, so your #1 idea is clean and reasonable. Cheers! > On 18 Jul 2014, at 12:33 am, Szczepan Faber <szcze...@gmail.com> wrote: > > Hey guys, > > Currently configured default findbugs version (2.0.3) is not happy > with java 8. Newest findbugs (3.0.0) enjoys java 8 but requires java 7 > (http://findbugs.sourceforge.net/). I suggest we encapsulate this in > the plugin so that findbugs has higher chance to work out of the box > for Gradle users. So, if current java is < 1.7, we use findbugs 2.0.3, > else 3.0.0. > > Thoughts? > -- > Szczepan Faber > Core dev@gradle; Founder@mockito > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > CTO Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > > > -- Szczepan Faber Core dev@gradle; Founder@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
