Re: Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-05-04 Thread Russel Winder
On Sat, 2014-05-03 at 16:03 -0300, Miguel Landaeta wrote: […] > > FYI: If there are not objections and I don't stumble upon any other > blocker issue, I intend to upload groovy2 package during the next week > to unstable. > That works for me. Gradle 1.12 was released a few days ago. It will be

Re: Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-05-03 Thread Miguel Landaeta
tags 746253 + pending tags 744337 + pending tags 745815 + pending thanks On Sat, Apr 19, 2014 at 10:00:33AM -0300, Miguel Landaeta wrote: > > I just raised the voice on this gradle/groovy situation because > after my groovy 1.8.6-2 upload gradle is not working anymore and > I'm looking for more

Re: Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-19 Thread Miguel Landaeta
Thanks everybody for their input. On Fri, Apr 18, 2014 at 05:54:17PM +0200, Emmanuel Bourg wrote: > > Thanks to your explanations it becomes clear I think that we must > package groovy 2 separately, and keep the original groovy package at > version 1.8.6 until the transition to Gradle 2 is comple

Re: Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-18 Thread Russel Winder
On Fri, 2014-04-18 at 17:54 +0200, Emmanuel Bourg wrote: > Thank you for stepping in Russel. No problem, glad to help. > Just to clarify the "unique version policy" isn't an absolute > requirement. If it's necessary multiple versions of an application or > library can be packaged (for example JUn

Re: Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-18 Thread Eric L.
Hi, On 18/04/14 17:18, Russel Winder wrote: The core problem here with the Java and Groovy support on Debian is the policy of one and only one version, and no use of Maven Central or Bintray/jCentre for build. I am not aware of any such policy as "one and only one version": one could have a "gr

Re: Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-18 Thread Emmanuel Bourg
Thank you for stepping in Russel. Just to clarify the "unique version policy" isn't an absolute requirement. If it's necessary multiple versions of an application or library can be packaged (for example JUnit 3 and 4, Maven 2 and 3, Tomcat 6&7&8, ASM 3 and 4, etc). Thanks to your explanations it

Re: Bug#733234: Groovy fails with groovy.lang.MissingMethodException

2014-04-18 Thread Russel Winder
On Fri, 2014-04-18 at 00:44 +0100, Stephen Nelson wrote: […] > > I'm looking at this too, as it stops work on building Spring using > Gradle. I updated groovy to 1.8.9, and still gradle fails. So I > thought about including the required dependencies to enable the groovy > tests. This will prove th