Surely Groovy is widely used with security managers, and it has never been a problem so far. I'm not sure how this issue is relevant to the problem, but Jochen expressed several times concerns about how Groovy would interact with Jigsaw without getting clear answers, or at best "we don't know". I'm unfortunately not in a position where I can investigate right now, but Jigsaw is certainly critical for both Groovy and Gradle, so I'd like to make sure we address all issues before Jigsaw is out. Basically my focus today is making Gradle capable of building apps using Jigsaw, but not running on Jigsaw. Just because those are competing priorities. But both *have* to be fixed.
2015-11-02 11:24 GMT+01:00 Alan Bateman <alan.bate...@oracle.com>: > > On 02/11/2015 09:58, Cédric Champeau wrote: > >> >> I think this is the particular issue Jochen is very worried about. We >> should think about the consequences of it. What does it mean to be forced >> to use -XaddExports. It is at least unclear to me. What would be >> catastrophic is releasing Jigsaw and realizing that we killed Groovy >> because it cannot use modules without, for example, disabling all kind of >> security. >> > > Uwe Schindler has created a bug on this topic here: > > https://issues.apache.org/jira/browse/GROOVY-7587 > > It makes me wonder if Groovy has ever been used with a security manager as > it seems to wrap or need access to all JDK-internal types. > > -Alan. >
