Re: JDK9 Modules

Ah, makes sense. I brought this up to them. They have updated the PPA ( https://launchpad.net/~webupd8team/+archive/ubuntu/java) to specify that it is using the regular JDK not the jigsaw build; with a link to the jigsaw build. Malachi de Ælfweald http://www.google.com/profiles/malachid On

Re: JDK9 Modules

On 12/07/2016 22:24, Malachi de Ælfweald wrote: I notice that with 9-ea+125-2016-07-06-073258.javare.5251.nc , this works: --add-modules=ALL-SYSTEM --add-exports=java.base/sun.nio.ch =ALL-UNNAMED With a slightly newer 9-ea+126

Re: JDK9 Modules

I notice that with 9-ea+125-2016-07-06-073258.javare.5251.nc, this works: --add-modules=ALL-SYSTEM --add-exports=java.base/sun.nio.ch=ALL-UNNAMED With a slightly newer 9-ea+126 from webupd8, it causes: Unrecognized option: --add-modules=ALL-SYSTEM Do we need to ask that the WebUpd8 team build

Re: JDK9 Modules

Verified that the following works with 9-ea+ 125-2016-07-06-073258.javare.5251.nc export _JAVA_OPTIONS="--add-modules=ALL-SYSTEM --add-exports=java.base/ sun.nio.ch=ALL-UNNAMED" Malachi de Ælfweald http://www.google.com/profiles/malachid On Wed, Jul 6, 2016 at 8:03 AM, Malachi de Ælfweald

Re: JDK9 Modules

Since the -addmods didn't work from within the options.compilerArgs, I thought I would check if these temporary jdk.launcher ones would work there instead of in _JAVA_OPTIONS. No go with that option. Also, interesting side note - I have the _JAVA_OPTIONS specified in my .bashrc, so it is picking

Re: JDK9 Modules

I think I must be misunderstanding your suggestion. If I do: export _JAVA_OPTIONS="--add-modules=ALL-SYSTEM --add-exports=java.base/ sun.nio.ch=ALL-UNNAMED" then: java -version reports: Unrecognized option: --add-modules=ALL-SYSTEM Error: Could not create the Java Virtual Machine. Error: A fatal

Re: JDK9 Modules

On 05/07/2016 22:24, Malachi de Ælfweald wrote: With: export _JAVA_OPTIONS="-Djdk.launcher.addmods=ALL-SYSTEM -Djdk.launcher.addexports.0=java.base/sun.nio.ch=ALL-UNNAMED" no GRADLE_OPTIONS no options.compilerArgs in build.gradle 1. The dagger project compiles and runs 2. The neo4j project

Re: JDK9 Modules

> and monotonically increase with no gaps, and maintain that over time with > packages added/deleted). > > > > *From:* Malachi de Ælfweald [mailto:malac...@gmail.com] > *Sent:* Tuesday, July 05, 2016 5:24 PM > > *To:* Stephen Felts > *Cc:* Remi Forax; jigsaw-dev@openjdk.jav

RE: JDK9 Modules

@openjdk.java.net Subject: Re: JDK9 Modules   With: export _JAVA_OPTIONS="-Djdk.launcher.addmods=ALL-SYSTEM -Djdk.launcher.addexports.0=java.base/HYPERLINK "http://sun.nio.ch"sun.nio.ch=ALL-UNNAMED; no GRADLE_OPTIONS no options.compilerArgs in build.gradle 1. The dagger project co

Re: JDK9 Modules

you need comma separated or java.se.ee. > > > > > > *From:* Malachi de Ælfweald [mailto:malac...@gmail.com] > *Sent:* Tuesday, July 05, 2016 5:00 PM > > *To:* Stephen Felts > *Cc:* Remi Forax; jigsaw-dev@openjdk.java.net > *Subject:* Re: JDK9 Modules > > > >

RE: JDK9 Modules

@openjdk.java.net Subject: Re: JDK9 Modules   oh lol! I thought you were just italicizing! ;) That seemed to fix the Dagger one. Now let me try to back off of all the changes and figure out what the minimal configuration is. Malachi de Ælfweald http://www.google.com/profiles/malachid   On Tue

Re: JDK9 Modules

<stephen.fe...@oracle.com> wrote: > Well you need the leading underscore. > > > > *From:* Malachi de Ælfweald [mailto:malac...@gmail.com] > *Sent:* Tuesday, July 05, 2016 4:36 PM > > *To:* Stephen Felts > *Cc:* Remi Forax; jigsaw-dev@openjdk.java.net > *Subje

RE: JDK9 Modules

Subject: Re: JDK9 Modules Regarding the Neo4j one, I tried adding '-XaddExports:java.base/sun.nio.ch=ALL-UNNAMED' to both build.gradle and jdk9args, but it still says: Caused by: java.lang.IllegalAccessError: class org.neo4j.io.pagecache.impl.SingleFilePageSwapper (in unnamed module @0x49070868) cannot

Re: JDK9 Modules

Regarding the Neo4j one, I tried adding '-XaddExports:java.base/sun.nio.ch=ALL-UNNAMED' to both build.gradle and jdk9args, but it still says: Caused by: java.lang.IllegalAccessError: class org.neo4j.io.pagecache.impl.SingleFilePageSwapper (in unnamed module @0x49070868) cannot access class

RE: JDK9 Modules

Well you need the leading underscore.   From: Malachi de Ælfweald [mailto:malac...@gmail.com] Sent: Tuesday, July 05, 2016 4:36 PM To: Stephen Felts Cc: Remi Forax; jigsaw-dev@openjdk.java.net Subject: Re: JDK9 Modules   adding that (without the leading underscore) I still get

Re: JDK9 Modules

t; > export _*JAVA*_OPTIONS=”-Djdk.launcher.addmods=ALL-SYSTEM” > > > > > > > > *From:* Malachi de Ælfweald [mailto:malac...@gmail.com] > *Sent:* Tuesday, July 05, 2016 3:29 PM > > *To:* Stephen Felts > *Cc:* Remi Forax; jigsaw-dev@openjdk.java.net > *Subject:* R

Re: JDK9 Modules

t; > GRADLE_OPTS=@/mydir/jdk9args -Xmx2048m > -Dorg.gradle.jvmargs="@/mydir/jdk9args -Xmx2048m " > > > > *From:* Malachi de Ælfweald [mailto:malac...@gmail.com] > *Sent:* Tuesday, July 05, 2016 1:52 PM > *To:* Stephen Felts > *Cc:* Remi Forax; jigsaw-dev@o

Re: JDK9 Modules

he > individual module level to -addmods java.xml.bind. > > > > -----Original Message- > From: Malachi de Ælfweald [mailto:malac...@gmail.com] > Sent: Tuesday, July 05, 2016 4:15 AM > To: Remi Forax > Cc: jigsaw-dev@openjdk.java.net > Subject: Re: JDK

RE: JDK9 Modules

e I need java.xml.bind and I can't just re-set it at the individual module level to -addmods java.xml.bind. -Original Message- From: Malachi de Ælfweald [mailto:malac...@gmail.com] Sent: Tuesday, July 05, 2016 4:15 AM To: Remi Forax Cc: jigsaw-dev@openjdk.java.net Subject: Re:

Re: JDK9 Modules

Hi Alan, On Tue, Jul 5, 2016 at 1:03 AM, Alan Bateman wrote: > On 05/07/2016 08:00, Malachi de Ælfweald wrote: > > : >> >> Neo4j fails due to internal Sun classes being used: >> cannot access class sun.nio.ch.FileChannelImpl (in module java.base) >> because module

Re: JDK9 Modules

2 AM, Remi Forax <fo...@univ-mlv.fr> wrote: > - Mail original - > > De: "Malachi de Ælfweald" <malac...@gmail.com> > > À: jigsaw-dev@openjdk.java.net > > Envoyé: Mardi 5 Juillet 2016 09:00:22 > > Objet: JDK9 Modules > > > > While I u

Re: JDK9 Modules

On 05/07/2016 08:00, Malachi de Ælfweald wrote: : Neo4j fails due to internal Sun classes being used: cannot access class sun.nio.ch.FileChannelImpl (in module java.base) because module java.base does not export sun.nio.ch to unnamed module @0x6166e06f In this case then I assume the exception

Re: JDK9 Modules

- Mail original - > De: "Malachi de Ælfweald" <malac...@gmail.com> > À: jigsaw-dev@openjdk.java.net > Envoyé: Mardi 5 Juillet 2016 09:00:22 > Objet: JDK9 Modules > > While I understand the motivation behind making the system more modular, I > am having

JDK9 Modules

While I understand the motivation behind making the system more modular, I am having a bit of a problem understanding how to use it with existing 3rd party APIs. I saw the email thread with Alan and Stephen discussing how there was a need to test some of the tools. Over the last couple weeks, I

Re: Ant JunitTask update to support JDK9 modules

them on the ant-dev mailing list in the context of Apache Ant >> in >> http://mail-archives.apache.org/mod_mbox/ant-dev/201604.mbox/%3cafe6c849-0622-44d1-9ff7-3a6ca4832...@oracle.com%3E >> As a result of the discussion I've created a pull request for Apache Ant >> JUnitT

Re: Ant JunitTask update to support JDK9 modules

> On 27 Apr 2016, at 23:26, Alex Buckley wrote: > > On 4/27/2016 1:41 PM, Jan Lahoda wrote: >> On 27.4.2016 21:30, Alex Buckley wrote: >>> Your changes skyrocket in complexity because your Ant setup involves >>> both ant-junit.jar and ant-junit4.jar. The JUnit task

Re: Ant JunitTask update to support JDK9 modules

/%3cafe6c849-0622-44d1-9ff7-3a6ca4832...@oracle.com%3E As a result of the discussion I've created a pull request for Apache Ant JUnitTask to support JDK9 modules: https://github.com/apache/ant/pull/18 On the qualified export approach then one thing you say is that it requires compiling

Re: Ant JunitTask update to support JDK9 modules

Hi, I previously proposed module group concept that its member modules can be loaded by same classloader. If one module doesn't define its module goup, that defaulted to module's name. module ant.junit{ group: ant.junit; //this can be emitted: default values is module name } module

Re: Ant JunitTask update to support JDK9 modules

On 4/27/2016 1:41 PM, Jan Lahoda wrote: On 27.4.2016 21:30, Alex Buckley wrote: Your changes skyrocket in complexity because your Ant setup involves both ant-junit.jar and ant-junit4.jar. The JUnit task documentation (https://ant.apache.org/manual/Tasks/junit.html) doesn't suggest this is

Re: Ant JunitTask update to support JDK9 modules

request for Apache Ant JUnitTask to support JDK9 modules: https://github.com/apache/ant/pull/18 Thanks for comments! I will link them back to the pull request. -- Tomas