Vote: Yes
On 9/15/2015 12:28 AM, Mike Duigou wrote:
Vote: YES
On 2015-09-11 12:43, jigsaw-dev-requ...@openjdk.java.net wrote:
From: Karen Kinnear
To: jigsaw-dev
Subject: CFV: New Jigsaw Committer: Harold Seigel
Message-ID: <7f587027-2bdb-4c37-9fd7-01aebfb17...@oracle.com>
Content-Type: text/
Changeset: 86ed8a85486d
Author:vromero
Date: 2015-09-14 18:23 -0700
URL: http://hg.openjdk.java.net/jigsaw/jake/langtools/rev/86ed8a85486d
add missing file
+ src/jdk.compiler/share/classes/com/sun/tools/javac/util/ModuleHelper.java
Changeset: 7cba4b9b9595
Author:vromero
Date: 2015-09-14 18:18 -0700
URL: http://hg.openjdk.java.net/jigsaw/jake/langtools/rev/7cba4b9b9595
New hidden option to expose javac internal API to processors
!
src/jdk.compiler/share/classes/com/sun/tools/javac/processing/JavacProcessingEn
https://bugs.openjdk.java.net/browse/JDK-8136505
-- Jon
On 09/14/2015 01:22 AM, Peter Levart wrote:
Hi,
I experimented a little with EA build and found javac behaving a
little strange. Is this known or expected behaviour?
For example, having the following layout of sources:
modsrc/modA/mod
On 09/13/2015 11:54 AM, Martin Buchholz wrote:
javadoc does not seem to have any support for -Xmodule, so I don't know how
to fix the "docs" target.
https://bugs.openjdk.java.net/browse/JDK-8136503
-- Jon
On 09/13/2015 06:25 AM, Alan Bateman wrote:
On 12/09/2015 20:16, Jayaprakash Arthanareeswaran wrote:
Hello experts,
With JDK 9, some of JDT Core tests have started failing. The failing
tests
are in the JSR 199 area, where we test Eclipse's compiler in a mixed
mode
with Javac's StandardJav
Op Mon, 14 Sep 2015 20:27:39 +0200 schreef Alan Bateman
:
On 14/09/2015 17:40, Robert Scholte wrote:
Hi,
On behalf of the Apache Maven team I'd like to ask for advice for
changing the JavaxToolsCompiler[1]
This implementation is used when java code is being compiled with Maven
*by defaul
On 09/14/2015 12:44 PM, Alan Bateman wrote:
On 14/09/2015 20:21, Stuart McCulloch wrote:
Yes, the issue is that ToolProvider.getSystemJavaCompiler() is
returning null when using the Jigsaw EA with Maven.
AFAICT this is because it’s now using the service loader mechanism
which is influenced
On 14/09/2015 20:21, Stuart McCulloch wrote:
Yes, the issue is that ToolProvider.getSystemJavaCompiler() is returning null
when using the Jigsaw EA with Maven.
AFAICT this is because it’s now using the service loader mechanism which is
influenced by the Thread’s context ClassLoader
That ma
On 09/14/2015 11:14 AM, Alan Bateman wrote:
On 14/09/2015 09:22, Peter Levart wrote:
:
Gives the following runtime error:
Exception in thread "main" java.lang.IllegalAccessError: class
pkgA.TestA (in module: modA) cannot access class pkgC.TypeC (in
module: modC), modA cannot read modC
Yes, the issue is that ToolProvider.getSystemJavaCompiler() is returning null
when using the Jigsaw EA with Maven.
AFAICT this is because it’s now using the service loader mechanism which is
influenced by the Thread’s context ClassLoader
The following patch to make sure Maven uses the system
Vote: YES
On 2015-09-14 01:22, jigsaw-dev-requ...@openjdk.java.net wrote:
Date: Sun, 13 Sep 2015 15:33:48 +0100
From: Alan Bateman
To: jigsaw-dev
Subject: CFV: New jigsaw Committer: Jean-Francois Denise
Message-ID: <55f5894c.4090...@oracle.com>
Content-Type: text/plain; charset=utf-8; format=
Vote: YES
On 2015-09-11 12:43, jigsaw-dev-requ...@openjdk.java.net wrote:
From: Karen Kinnear
To: jigsaw-dev
Subject: CFV: New Jigsaw Committer: Harold Seigel
Message-ID: <7f587027-2bdb-4c37-9fd7-01aebfb17...@oracle.com>
Content-Type: text/plain; charset=us-ascii
I hereby nominate Haro
On 14/09/2015 17:40, Robert Scholte wrote:
Hi,
On behalf of the Apache Maven team I'd like to ask for advice for
changing the JavaxToolsCompiler[1]
This implementation is used when java code is being compiled with
Maven *by default*, so right now when pointing JAVA_HOME to the latest
JDK9 ver
On 14/09/2015 17:48, Rahman USTA wrote:
|jlink --modulepath %JAVA_HOME%/jmods;mlib --addmods com.greetings
--output greetingsapp|
After last step, greetingsapp folder generated with all Jigsaw
modules. How can I include just base mod or other compact mods ?
I assume what you are seein
Hi,
On behalf of the Apache Maven team I'd like to ask for advice for changing
the JavaxToolsCompiler[1]
This implementation is used when java code is being compiled with Maven
*by default*, so right now when pointing JAVA_HOME to the latest JDK9
version builds will fail.
There are other wa
Vote: yes
Hi Alan,
Thanks for the update - I recollect Jon's email about jtreg needing some
work.
Cheers,
Mani
On Mon, Sep 14, 2015 at 12:51 PM, Alan Bateman
wrote:
> On 14/09/2015 12:30, Mani Sarkar wrote:
>
>> Hi all,
>>
>> Project Jigsaw JDK & JRE binaries + test results are now available on the
>> A
On 14/09/2015 12:30, Mani Sarkar wrote:
Hi all,
Project Jigsaw JDK & JRE binaries + test results are now available on the
Adopt OpenJDK Cloudbees Build farm:
https://adopt-openjdk.ci.cloudbees.com/view/OpenJDK/job/project-jigsaw-openjdk-1.9-linux-x86_64/lastSuccessfulBuild/artifact/
Hi Mani,
Hi all,
Project Jigsaw JDK & JRE binaries + test results are now available on the
Adopt OpenJDK Cloudbees Build farm:
https://adopt-openjdk.ci.cloudbees.com/view/OpenJDK/job/project-jigsaw-openjdk-1.9-linux-x86_64/lastSuccessfulBuild/artifact/
Please share with your communities.
Cheers,
Mani
-
On 14/09/2015 09:22, Peter Levart wrote:
:
Gives the following runtime error:
Exception in thread "main" java.lang.IllegalAccessError: class
pkgA.TestA (in module: modA) cannot access class pkgC.TypeC (in
module: modC), modA cannot read modC
at pkgA.TestA.main(modA@/TestA.java:8)
W
Hi,
I experimented a little with EA build and found javac behaving a little
strange. Is this known or expected behaviour?
For example, having the following layout of sources:
modsrc/modA/module-info.java
module modA {
requires modB;
}
modsrc/modA/pkgA/TestA.java
package
22 matches
Mail list logo
