I've seen the announcement about Gradle 2 getting out with Groovy 2.
Congratulations for all the hard work and thank you for taking time to
for this. I hope it's enough time to make it in Debian Jessie before
the freeze.

Regards,

On Wed, Apr 30, 2014 at 4:49 AM, Adam Murdoch
<adam.murd...@gradleware.com> wrote:
>
> On 29 Apr 2014, at 6:23 pm, Ioan Eugen Stan <stan.ieu...@gmail.com> wrote:
>
> Hell Daz,
>
> It's about 10 tests in 5 files commented, out of a few hundred. So
> it's quite a small change. I don't have the time to dive deep in
> Gradle. It's a too big of comitement to me and someone with more
> Gradle experience will no doubt solve it much faster.
>
>
> I’ve started to look at this, and pushed a few compilation fixes. Haven’t
> pushed the change to Groovy 2.x yet.
>
> I’ll try to push more fixes over the next week or so and then finally switch
> to Groovy 2.x.
>
>
> Good luck. I hope gradle 2 gets out fast.
>
>
> Me too.
>
> Thanks for your help in getting the ball rolling on the switch to Groovy
> 2.x.
>
>
>
> Regards,
>
> On Thu, Apr 24, 2014 at 9:28 PM, Daz DeBoer
> <darrell.deb...@gradleware.com> wrote:
>
> 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
>
> Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA:
> http://www.gradlesummit.com
>
>
>
>
> --
> Ioan Eugen Stan
> 0720 898 747
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
>
> --
> Adam Murdoch
> Gradle Co-founder
> http://www.gradle.org
> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
> http://www.gradleware.com
>
> Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA:
> http://www.gradlesummit.com
>



-- 
Ioan Eugen Stan
0720 898 747

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to