Build futures

[Russel Winder-3]

When (not if I hope) Groovy gets a Gradle build as it's primary build,
will the plan be to integrate the native launcher and build it using the
C/C++ build tool for Gradle?
--
Russel.
=============================================================================
Dr Russel Winder      t: [phone]   voip: sip:[hidden email]
41 Buckmaster Road    m: [phone]   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

[Guillaume Laforge-4]

It's not been planed to build the native launcher, but that might be possible.

Currently, we're stuck with Ant, as there's a bug in Gradle that hangs the build when executing the tests.

On Thu, May 3, 2012 at 9:38 PM, Russel Winder <[hidden email]> wrote:

When (not if I hope) Groovy gets a Gradle build as it's primary build,
will the plan be to integrate the native launcher and build it using the
C/C++ build tool for Gradle?
--
Russel.
=============================================================================
Dr Russel Winder      t: <a href="tel:%2B44%2020%207585%202200" value="[phone]">[phone]   voip: [hidden email]
41 Buckmaster Road    m: <a href="tel:%2B44%207770%20465%20077" value="[phone]">[phone]   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

[Russel Winder-3]

On Thu, 2012-05-03 at 21:55 +0200, Guillaume Laforge wrote:
> It's not been planed to build the native launcher, but that might be
> possible.
> Currently, we're stuck with Ant, as there's a bug in Gradle that hangs the
> build when executing the tests.

I would have thought that Gradle could not have got to 1.0-RC-3 with a
known bug in a so closely connected project?  It cannot be that Gralde
release 1.0 and Groovy cannot be built with it.

--
Russel.
=============================================================================
Dr Russel Winder      t: [phone]   voip: sip:[hidden email]
41 Buckmaster Road    m: [phone]   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

[Guillaume Laforge]

Well, unfortunately... This is the case.

Guillaume

Le 4 mai 2012 à 09:17, Russel Winder <[hidden email]> a écrit :

> On Thu, 2012-05-03 at 21:55 +0200, Guillaume Laforge wrote:
>> It's not been planed to build the native launcher, but that might be
>> possible.
>> Currently, we're stuck with Ant, as there's a bug in Gradle that hangs the
>> build when executing the tests.
>
> I would have thought that Gradle could not have got to 1.0-RC-3 with a
> known bug in a so closely connected project?  It cannot be that Gralde
> release 1.0 and Groovy cannot be built with it.
>
> --
> Russel.
> =============================================================================
> Dr Russel Winder      t: [phone]   voip: sip:[hidden email]
> 41 Buckmaster Road    m: [phone]   xmpp: [hidden email]
> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Russel Winder-3]

On Fri, 2012-05-04 at 09:23 +0200, Guillaume Laforge wrote:
> Well, unfortunately... This is the case.

Marketing nightmare for Gradle then.

"Here is the shiny new Gradle 1.0, Oh by the way it is impossible to
build Groovy, the language of Gradle, using Gradle."

Reddit, etc. will make hay with this.

--
Russel.
=============================================================================
Dr Russel Winder      t: [phone]   voip: sip:[hidden email]
41 Buckmaster Road    m: [phone]   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

[Guillaume Laforge-4]

Perhaps you can influence our Gradle friends and encourage to have a closer look at that issue before their final release?

http://issues.gradle.org/browse/GRADLE-2170

Guillaume

On Fri, May 4, 2012 at 10:09 AM, Russel Winder <[hidden email]> wrote:

On Fri, 2012-05-04 at 09:23 +0200, Guillaume Laforge wrote:
> Well, unfortunately... This is the case.

Marketing nightmare for Gradle then.

"Here is the shiny new Gradle 1.0, Oh by the way it is impossible to
build Groovy, the language of Gradle, using Gradle."

Reddit, etc. will make hay with this.

--
Russel.
=============================================================================
Dr Russel Winder      t: <a href="tel:%2B44%2020%207585%202200" value="[phone]">[phone]   voip: [hidden email]
41 Buckmaster Road    m: <a href="tel:%2B44%207770%20465%20077" value="[phone]">[phone]   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

As I've said multiple times now, it's a bug that Gradle hangs in this case but fixing that won't make the tests run.

The security policy that the tests use has to be wrong, because it's restricting Gradle in a way that it could never work.

On 04/05/2012, at 1:16 AM, Guillaume Laforge <[hidden email]> wrote:

Perhaps you can influence our Gradle friends and encourage to have a closer look at that issue before their final release?

http://issues.gradle.org/browse/GRADLE-2170

Guillaume

On Fri, May 4, 2012 at 10:09 AM, Russel Winder <[hidden email]> wrote:

On Fri, 2012-05-04 at 09:23 +0200, Guillaume Laforge wrote:
> Well, unfortunately... This is the case.

Marketing nightmare for Gradle then.

"Here is the shiny new Gradle 1.0, Oh by the way it is impossible to
build Groovy, the language of Gradle, using Gradle."

Reddit, etc. will make hay with this.

--
Russel.
=============================================================================
Dr Russel Winder      t: <a href="tel:%2B44%2020%207585%202200" value="[phone]">[phone]   voip: [hidden email]
41 Buckmaster Road    m: <a href="tel:%2B44%207770%20465%20077" value="[phone]">[phone]   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

[Jochen Theodorou]

Am 04.05.2012 15:41, schrieb Luke Daley:
> As I've said multiple times now, it's a bug that Gradle hangs in this
> case but fixing that won't make the tests run.
>
> The security policy that the tests use has to be wrong, because it's
> restricting Gradle in a way that it could never work.

First it has to be said to Russel... it is possible to compile Groovy
using gradle, but the SecurityTestSuit will hang because if some strange
conflict.

and then in general... isn't it possible to run the security test in a
forked JVM without too much influence from gradle? Wouldn't the test
then work? forkEvery=1 would do that, or not?

but actually we use that already... maybe wrong?

bye blackdrag

--
Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.org


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Cédric Champeau]

To be honest, the problem is more that the build hangs more than the
test failing (the test currently often fails on Bamboo with the ant
build). And it hangs because Gradle fails to release a countdown latch.
Even if the groovy build uses a custom security configuration (I noticed
that it already has some gradle specific hacks, but I'm really no
expert), there's a problem with Gradle not releasing that latch.

Le 04/05/2012 16:18, Jochen Theodorou a écrit :

> Am 04.05.2012 15:41, schrieb Luke Daley:
>> As I've said multiple times now, it's a bug that Gradle hangs in this
>> case but fixing that won't make the tests run.
>>
>> The security policy that the tests use has to be wrong, because it's
>> restricting Gradle in a way that it could never work.
>
> First it has to be said to Russel... it is possible to compile Groovy
> using gradle, but the SecurityTestSuit will hang because if some
> strange conflict.
>
> and then in general... isn't it possible to run the security test in a
> forked JVM without too much influence from gradle? Wouldn't the test
> then work? forkEvery=1 would do that, or not?
>
> but actually we use that already... maybe wrong?
>
> bye blackdrag
>

--
Cédric Champeau
SpringSource - A Division Of VMware
http://www.springsource.com/
http://twitter.com/CedricChampeau


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Jochen Theodorou]

Am 04.05.2012 16:24, schrieb Cédric Champeau:
> To be honest, the problem is more that the build hangs more than the
> test failing (the test currently often fails on Bamboo with the ant
> build). And it hangs because Gradle fails to release a countdown latch.
> Even if the groovy build uses a custom security configuration (I noticed
> that it already has some gradle specific hacks, but I'm really no
> expert), there's a problem with Gradle not releasing that latch.

but if the test is executed in a forked JVM gradle should not have an
influence on that, should it?

bye blackdrag


--
Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.org


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

On 04/05/2012, at 7:24 AM, Cédric Champeau wrote:

> To be honest, the problem is more that the build hangs more than the test failing (the test currently often fails on Bamboo with the ant build). And it hangs because Gradle fails to release a countdown latch.

Going from memory, and it's been a while… it fails to release the latch because it gets a security exception trying to do something.

> Even if the groovy build uses a custom security configuration (I noticed that it already has some gradle specific hacks, but I'm really no expert), there's a problem with Gradle not releasing that latch.

Right, so you'd get a failure but definitely not passing tests.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

On 04/05/2012, at 8:49 AM, Jochen Theodorou wrote:

> Am 04.05.2012 16:24, schrieb Cédric Champeau:
>> To be honest, the problem is more that the build hangs more than the
>> test failing (the test currently often fails on Bamboo with the ant
>> build). And it hangs because Gradle fails to release a countdown latch.
>> Even if the groovy build uses a custom security configuration (I noticed
>> that it already has some gradle specific hacks, but I'm really no
>> expert), there's a problem with Gradle not releasing that latch.
>
> but if the test is executed in a forked JVM gradle should not have an influence on that, should it?

Gradle does have a lot of influence in the forked JVM. We manage the test execution process.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Russel Winder-3]

On Fri, 2012-05-04 at 16:18 +0200, Jochen Theodorou wrote:
[...]
> First it has to be said to Russel... it is possible to compile Groovy
> using gradle, but the SecurityTestSuit will hang because if some strange
> conflict.

The Gradle build has an installAll target which works wonderfully.
Success for the Groovy build is when I can do:

        gradlew clean installAll && gradlew clean

for Groovy just as I do for Gradle.  Currently I have a shell script so:

        ant clean && installGroovy && ant clean

this is archaic and must go.

[...]

--
Russel.
=============================================================================
Dr Russel Winder      t: [phone]   voip: sip:[hidden email]
41 Buckmaster Road    m: [phone]   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

[Cédric Champeau]

Also, please note that the up-to-date Gradle build is only on the
"modularisation" branch, which should be merged into master only after
rework is finished. I don't know what the gradle build on master does,
but it's certainly not complete :)

Le 05/05/2012 10:54, Russel Winder a écrit :

> On Fri, 2012-05-04 at 16:18 +0200, Jochen Theodorou wrote:
> [...]
>> First it has to be said to Russel... it is possible to compile Groovy
>> using gradle, but the SecurityTestSuit will hang because if some strange
>> conflict.
> The Gradle build has an installAll target which works wonderfully.
> Success for the Groovy build is when I can do:
>
>          gradlew clean installAll && gradlew clean
>
> for Groovy just as I do for Gradle.  Currently I have a shell script so:
>
>          ant clean && installGroovy && ant clean
>
> this is archaic and must go.
>
> [...]
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Russel Winder-3]

On Sat, 2012-05-05 at 11:02 +0200, Cédric CHAMPEAU wrote:
> Also, please note that the up-to-date Gradle build is only on the
> "modularisation" branch, which should be merged into master only after
> rework is finished. I don't know what the gradle build on master does,
> but it's certainly not complete :)
[...]

I think the master build.gradle doesn't allow a build at all, I haven't
tried it in months.

Guillaume asked me to try the modularization branch a few weeks back, I
haven't had the opportunity to switch due to minimizing risk leading up
to ACCU 2012 last week. I should now give it a go, particularly leading
up to Gr8Conf.

--
Russel.
=============================================================================
Dr Russel Winder      t: [phone]   voip: sip:[hidden email]
41 Buckmaster Road    m: [phone]   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

[Jochen Theodorou]

Am 04.05.2012 16:24, schrieb Cédric Champeau:
> To be honest, the problem is more that the build hangs more than the
> test failing (the test currently often fails on Bamboo with the ant
> build). And it hangs because Gradle fails to release a countdown latch.
> Even if the groovy build uses a custom security configuration (I noticed
> that it already has some gradle specific hacks, but I'm really no
> expert), there's a problem with Gradle not releasing that latch.

have you tried the build with this in the policy file?

> grant  {
>     permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
> };

  bye blackdrag


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email