Hi Ioan Yes, we're committed to upgrading to Groovy 2.x for Gradle 2.0, which will be the next release of Gralde. Clearly, there are quite a few things that will need fixing and patching to make Gradle work with Groovy 2.x. In some cases the fix is a simple rename, but simply commenting out things isn't really going to cut it.
If you're willing to dive in deep to try to fix the underlying issues that would be great. Otherwise, somebody with more Groovy experience will probably need to take this on. Thanks Daz On Thu, Apr 24, 2014 at 3:43 AM, Ioan Eugen Stan <stan.ieu...@gmail.com>wrote: > Hello Adam, > > I've added Miguel (Debian Java Team) in CC. > > I've ran the tests again ignoring the cpp integration tests and things > work fain. The build fails when doing docs:test task. Core project > passes tests and integration tests and I presume the failure is due to > re-basing on an instable branch. > > I've ran: ./gradlew clean build -x cpp:integTest and got: > > ``` > * What went wrong: > Execution failed for task ':docs:test'. > ``` > Could you give it a try? The patch is pretty small. I didn't do much > besides ignoring and comenting out some tests. I don't have the > knowledge to fix them yet, and probably an existing committer would > fix them much faster. > > Given the facts above: any change in the policy adopting Groovy 2.x > for Gradle? Debian Jessie freezes sometime in November and we might > land Groovy 2.x if we move ok. > > Regards, > > -- > Ioan Eugen Stan > 0720 898 747 > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Darrell (Daz) DeBoer Principal Software Engineer, *Gradleware <http://gradleware.com>* Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com
