Hi Miguel,
2014-05-08 23:17 GMT+02:00 Miguel Landaeta :
> On Fri, Apr 18, 2014 at 12:51:38AM +0200, Bálint Réczey wrote:
>>
>> When there is a groovy - gradle pair in the archive which can build
>> itself I'll check back to this problem again.
>
> I believe gradle and groovy are now fixed in unsta
On Fri, Apr 18, 2014 at 12:51:38AM +0200, Bálint Réczey wrote:
>
> When there is a groovy - gradle pair in the archive which can build
> itself I'll check back to this problem again.
I believe gradle and groovy are now fixed in unstable, so please
ping me when you have the chance to revisit this
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
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
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
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
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
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
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
On Fri, Apr 18, 2014 at 12:33 AM, Miguel Landaeta wrote:
> Hi Bálint,
>
> On Fri, Apr 18, 2014 at 12:51:38AM +0200, Bálint Réczey wrote:
>> >
>> > Sorry I can't be more useful for this bug at this moment.
> If I uploaded groovy 2.2.1 to unstable now I would break gradle and
> groovy itself by caus
Hi Bálint,
On Fri, Apr 18, 2014 at 12:51:38AM +0200, Bálint Réczey wrote:
> >
> > Sorry I can't be more useful for this bug at this moment.
> I tried building groovy 2.2.1 on testing and it failed, too. I agree
> that 2.x is the way to go and I think you could find a state of sid on
> snapshots.de
Hi Miguel,
2014-04-17 20:33 GMT+02:00 Miguel Landaeta :
> tags 733234 + moreinfo
> thanks
>
> Hi Bálint,
>
> On Fri, Dec 27, 2013 at 04:28:39PM +0100, Bálint Réczey wrote:
>> Package: groovy
>> Version: 1.8.6-1
>> Severity: normal
>>
>> Hi,
>>
>> Using groovy to generate code in XBMC build fails.
tags 733234 + moreinfo
thanks
Hi Bálint,
On Fri, Dec 27, 2013 at 04:28:39PM +0100, Bálint Réczey wrote:
> Package: groovy
> Version: 1.8.6-1
> Severity: normal
>
> Hi,
>
> Using groovy to generate code in XBMC build fails.
Sorry for my delay to handle this bug.
To be honest, I'm not an expert
Hi,
On 12/27/2013 04:28 PM, Bálint Réczey wrote:
> Package: groovy
> Version: 1.8.6-1
> Severity: normal
>
> Hi,
>
> Using groovy to generate code in XBMC build fails.
>
> Steps to reproduce:
> apt-get -t experimental groovy
> apt-get build-dep xbmc
> dget http://http.debian.net/debian/pool/mai
Package: groovy
Version: 1.8.6-1
Severity: normal
Hi,
Using groovy to generate code in XBMC build fails.
Steps to reproduce:
apt-get -t experimental groovy
apt-get build-dep xbmc
dget http://http.debian.net/debian/pool/main/x/xbmc/xbmc_12.3+dfsg1-1.dsc
# if extraction fails
dpkg-source -x xbmc_1
15 matches
Mail list logo
