On 16.04.2016 19:16, Uwe Schindler wrote:
Hi,
You can still get a InputStream to bytecode of JDK-internal classes: if you get
the module of the Class and then call getResourceAsStream from there. I walked
that route for the forbidden-apis checker with reflection: This tool needs the
bytecode
Committer
Bremen, Germany
http://lucene.apache.org/
> -Original Message-
> From: Alan Bateman [mailto:alan.bate...@oracle.com]
> Sent: Saturday, April 16, 2016 10:31 PM
> To: Uwe Schindler ; jigsaw-dev@openjdk.java.net
> Subject: Re: running Groovy on JDK9
>
>
>
On 16/04/2016 18:16, Uwe Schindler wrote:
:
I would like to have an explanation by the OpenJDK developers, why Jigsaw no
longer returns jrt:// URL in ClassLoader#getResource on foreign modules - what
the reason for this?
This has come up several times and is tracked as #ClassFilesAsResources
6, 2016 5:24 PM
> To: jigsaw-dev@openjdk.java.net
> Subject: Re: running Groovy on JDK9
>
> On 10.04.2016 20:29, Jochen Theodorou wrote:
> [...]
>
> so another change in JDK9 makes tests failing and that is that I can no
> longer use ClassLoader#getResource to get an URL to
On 10.04.2016 20:29, Jochen Theodorou wrote:
[...]
so another change in JDK9 makes tests failing and that is that I can no
longer use ClassLoader#getResource to get an URL to a class. I remember
reading about this change here. I can work around this by using a class,
that does not originate fr
On 10.04.2016 20:29, Jochen Theodorou wrote:
[...]
Compile error during compilation with javac.
/tmp/stubgentests77510877964035184621460309483098/bar/GroovyClass.java:12:
error: package groovy.lang does not exist
groovy.lang.GroovyObject {
Looks like I actually found out why this happens. For
On 11/04/2016 16:57, Jochen Theodorou wrote:
:
Can it be registered via registerDriver? That actually made me wonder
why exactly we require the system loader here in the first place.
Part of the problem is DriverManager#getConnection, which is
@CallerSensitive. So if I want to get a connect
On 11/04/2016 16:57, Jochen Theodorou wrote:
:
And then of course there is the problem of XML parser being loaded
dynamically. You get effects like this:
https://bugs.openjdk.java.net/browse/JDK-8015099, and we too had
already a load of fun with xerces being part of the distribution and
the
On 4/13/2016 9:05 AM, Jochen Theodorou wrote:
What I would prefer though is a proper generic way to call a default
method on an interface without having an implementing instance. A
MethodHandles.lookup().in(Comperator.class) won't give me access to
invokespecial Comperator#reversed, or am I wrong
On 13.04.2016 14:10, Alan Bateman wrote:
On 11/04/2016 16:57, Jochen Theodorou wrote:
[...]
org.codehaus.groovy.runtime.InterfaceConversionTest >
testDefaultInterfaceMethodCallOnProxy FAILED
java.lang.AssertionError: java.util.Comparator/2
at
java.lang.invoke.MethodHandles$Lookup.
On 11/04/2016 16:57, Jochen Theodorou wrote:
:
Can it be registered via registerDriver? That actually made me wonder
why exactly we require the system loader here in the first place.
Part of the problem is DriverManager#getConnection, which is
@CallerSensitive. So if I want to get a connecti
On 10.04.2016 21:44, Alan Bateman wrote:
On 10/04/2016 19:29, Jochen Theodorou wrote:
Hi all,
today I had a few hours spare time and decided to invest that in
trying to make the Groovy build compile and run tests. I am not trying
to make a module on my own yet.
for compilation to work my bigg
properly handle
recursion).
-Original Message-
From: Stephen Felts
Sent: Sunday, April 10, 2016 3:50 PM
To: Jochen Theodorou; jigsaw-dev@openjdk.java.net
Subject: RE: running Groovy on JDK9
You should start with Gradle 2.10. It has most of the fixes needed to run with
JDK9.
I found that it
You should start with Gradle 2.10. It has most of the fixes needed to run with
JDK9.
I found that it was easiest to run with an argument file (though originally I
had it all on the command line).
It's needed for both gradle and the daemon.
export GRADLE_OPTS="@${argsfile} -Xmx2048m -Dorg.gradl
On 10/04/2016 19:29, Jochen Theodorou wrote:
Hi all,
today I had a few hours spare time and decided to invest that in
trying to make the Groovy build compile and run tests. I am not trying
to make a module on my own yet.
for compilation to work my biggest problem was the direct usage of the
15 matches
Mail list logo
