On Sun, Feb 23, 2014 at 3:25 AM, Ioan Eugen Stan <stan.ieu...@gmail.com>wrote:
> Hello, > > Short version question: What would it take to make gradle build with > groovy 2 - (before Debian Jessie Freeze at start of this November) ? > Short answer: we can't switch to Groovy 2 without breaking compiled plugins, and we have a strict backward compatibility standard for minor releases. Since we haven't deprecated support for Groovy 1.8.6, it's unlikely we'll remove support for this version in Gradle 2.0, our next major release. Instead, I believe the plan is to introduce the ability for Gradle to handle multiple Groovy versions. If this were done, it _should_ be possible to build and use Gradle on a platform that does not have 1.8.6 support (perhaps with some tweaks to enable this). But adding this ability will be a non-trivial undertaking. If you're still keen to help out we'd welcome the contribution, and I'm sure you'll find others who would also be willing to pitch in on this change. Daz > > I am interested in helping out. > > Long story, some of my reasoning and refined questions: > > I'm a software consultant/developer and I work mostly with Java/Groovy > and Maven. I'm also a Debian contributor and would like to see better > JVM support on Debian - going for Mainainer. I think that Groovy > (especially with Grapes) has a very important role, I won't go into > details here. > I also believe that many Debian maintainers prefer Gradle over Maven - > it seems that Gradle applications are easier to package with respect > to the Debian Policy which mandates all dependenies must also be > available as Debian packages. > > Debian (and Ubuntu) are very popular as development and production > platforms and people generally prefer and trust packages from main > distribution (stability and security). With this in mind, the two > distributions offer a very good distribution channel and will > encourage adoption of both Gradle and Groovy and the JVM. > > That being said, I would like to get Groovy 2 in Debian in time for > Jessie which is this November .Debian has a release cycle of ~ 2 > years, and no new major versions are added in the mean time so if it > doesn't make it now, it won't make it until the next release. > > The only problem is that Groovy 2 is built with Gradle which in turn > has a dependency on Groovy 1.8.x which is not good. Maintaining two > Groovy versions in Debian comes with a very big cost so the only > conclusion is - upgrade Gradle to Groovy. > > I'm a very good Java developer, ok with Groovy with ~ zero Gradle > knowledge and I would like to put some time in making the upgrade > provided: > > - it's doable (no major braking changes to the current version) > - you (community) are willing to integrate the changes upstream > - you (community) are willing to lend a hand to get me started - some > steps, what are the requirements for integrating the changes, etc. > > p.s. I may be biased on the above, but there is truth in there. > > -- > Ioan Eugen Stan > 0720 898 747 > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
