One more project lost for us thanks to gradle :( Alex ----- Original Message ----- > From: "Johannes Lips" <johannes.lips@xxxxxxxxx> > To: java-devel@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Thursday, July 5, 2012 9:32:14 AM > Subject: Re: Can we go to Groovy 2.0? > > Dan Allen wrote: > > Can we shoot for Groovy 2.0 in Fedora 18? What about Fedora 17 > > updates? > Hello Allen, > > I am currently co-maintaining groovy and I of course saw the new > update > as well. Although they claim all the changes are pretty minor and > nothing big, there is one thing preventing me from doing the update > right away. I tried that over the weekend but it was not possible. > The main reason is that they changed the whole build system from ant > to > gradlew [1] and I have to find the time to adopt those changes. > Main problem would be to get gradle in fedora first and then it might > be > possible to work on an update for groovy. > If there is another, easier way just let me know and I would be glad > implementing this. > > Johannes > > P.S.: Package review of gradle > https://bugzilla.redhat.com/show_bug.cgi?id=809950 > [1] http://www.gradle.org/ > > > > Groovy 2.0 is a crucial evolution in this widely used language and, > > being all about features first, we want Fedora to be the place to > > run it. > > > > The 2.0 update is significant because it introduces a static typing > > mode, allowing it to cater to both the dynamic language crowd as > > well as > > the traditional Java crowd. > > > > Of course, the big question for Fedora is backwards compatibility. > > Groovy 2.0 claims to be backwards compatible with 1.8. Hamlet > > D'Arcy had > > this to say on the topic in an abstract for an article on Groovy > > 2.0 in > > NFJS, The Magazine [1]: > > > > "Don’t worry, the major release is backwards compatible with > > previous > > Groovies. The 2.0 increment is earned because of the size and scope > > of > > its biggest features: modularization, invoke dynamic support, and > > most > > importantly an upgrade to the static type system. Groovy 2.0 will > > contain a static type checker which validates your code as part of > > the > > compiler, similar to what you’re familiar with from Java. The final > > class files and bytecode produced is still the same as before, but > > with > > this feature you have the safety you expect from Java with the > > conciseness and expressiveness of Groovy." > > > > Here's a detailed article published on InfoQ about what's new in > > Groovy > > 2.0. [2] > > > > -Dan > > > > [1] http://www.nofluffjuststuff.com/home/magazine_subscribe?id=31 > > [2] http://www.infoq.com/articles/new-groovy-20 > > > > -- > > Dan Allen > > Principal Software Engineer, Red Hat | Author of Seam in Action > > Registered Linux User #231597 > > > > http://google.com/profiles/dan.j.allen > > http://mojavelinux.com > > http://mojavelinux.com/seaminaction > > > > > > > > -- > > java-devel mailing list > > java-devel@xxxxxxxxxxxxxxxxxxxxxxx > > https://admin.fedoraproject.org/mailman/listinfo/java-devel > > > > > -- > java-devel mailing list > java-devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/java-devel -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel