Am 05.05.2012 09:59, schrieb Russel Winder:
On Fri, 2012-05-04 at 06:43 -0700, Luke Daley wrote:
Responded to on Groovy list.
Plain and simple, this issue is not going to be fixed for 1.0. It's also not
necessary to fix to make the Groovy build work.
So what is it that makes Guillaume think it's a Gradle problem not a
Groovy build problem? If we can get this sorted, we can get progress on
excising Ant from the Groovy build.
Well, if you read
http://gradle.1045684.n5.nabble.com/Infinite-wait-running-tests-td5561210.html
you will find Luke saying it is a gradle bug. Also, if you read the
quoted text above, Luke does not say there is no bug in gradle, he just
says that a fix for this is not needed to make the groovy build work.
In the nabble link you can read what happens, analyzed by Cedric. Why is
it a gradle problem? It worked before and now no longer does because
gradle needs additional permissions. Also the dump shows all kinds of
gradle messaging threads waiting for an event never to come.
I assume to make the Groovy build work we need to add this:
grant {
permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
};
to the policy file, with maybe the side effect of not all security tests
passing anymore. It would be nice to be able to limit the grant, but I
don't see how atm. Cedrics try with the codebase "file:${gradle.home}/-"
failed it seems.
bye blackdrag
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
