----- Original Message ----- > From: "Dan Allen" <dan.j.allen@xxxxxxxxx> > To: "Aleksandar Kurtakov" <akurtako@xxxxxxxxxx> > Cc: "Johannes Lips" <johannes.lips@xxxxxxxxx>, java-devel@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Thursday, July 5, 2012 10:55:00 AM > Subject: Re: Can we go to Groovy 2.0? > > On Thu, Jul 5, 2012 at 3:46 AM, Aleksandar Kurtakov < > akurtako@xxxxxxxxxx > wrote: > > > > One more project lost for us thanks to gradle :( > > > > There's no doubt, the adoption of Gradle has slowed down updates > until the packaging is complete. But, software is going to change, > that's just the nature of it. Nothing has been lost, we just have to > rise together to the new challenge. We could have said the same > thing about Maven builds before you all did the innovative work of > integrating that into rpmbuild. Sadly to support Gradle new blood is needed as the current maintainers are having hard time keeping Maven+friends up to date. Alex > > > It's becoming very clear to me, though, that we need to get more > information out there (this list is as good as any) on the status of > the Gradle packaging. That will help everyone set schedules and > expectations better. Let's frame it as a challenge, not a problem. > > > -Dan > > -- > > 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
