Yep, I think we need to be comfortable upgrading to newer versions of dependencies and tools unless there's a known breaking change in that dependency. So +1 from me.
On Thu, Jul 10, 2014 at 8:10 PM, Luke Daley <luke.da...@gradleware.com> wrote: > This would be my preference too. > > I think with one more +1 from a developer we should go ahead. > > On 10 July 2014 at 7:58:05 pm, Rene Groeschke (gra...@breskeby.com) wrote: > > IMO we should do this and add a note in the release notes about a possible > breaking change. > > cheers, > René > > > Luke Daley <luke.da...@gradleware.com> > 10 Jul 2014 11:04 > There’s an incompatibility with our default version of Jacoco and > JMockit: > http://forums.gradle.org/gradle/topics/jacocoplugin_makes_tests_fail_not_finding_junit_runner > > We’ve had two people report the same problem. It’s a bit nasty as it > causes the test execution to just hang with no feedback. > > Bumping the default jacoco versions would fix it. Could we do this? Or do > we deem this an incompatible change? > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Darrell (Daz) DeBoer http://www.gradleware.com
part1.05090906.03010602@breskeby
Description: Binary data
