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.
I can see the following options: 1. Change the default version to 3.0.0. Fail with a decent error if running on Java 6. 2. Leave the default where it is. Fail with a decent error if running on Java 8. 3. Select 3.0.0 if the project’s target java version is >= 1.7. Fail with a decent error if running on Java 6 (we should be doing this any way). If the project’s target java version is <= 1.7 or not declared default to 2.x. 4. One of the above, plus deprecate default versions, and require that the version be explicitly declared. I reckon we just go with #1. 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
