Re: jdeps --generate-open-module

> On May 15, 2017, at 12:43 PM, Sander Mak wrote: > > When executing `jdeps --generate-module-info ./out `, a module > descriptor exporting all packages is created. When using > `--generate-open-module`, a module descriptor with an open module is > generated, but no

AW: AW: Java 9 EA 169 Webstart NoClassDefFoundError: javax/xml/ws/Service

First, I want to say thanks for your help in this and the previous threads. > The JNLP fragment in my first mail can be used to resolve java.xml.ws > for JNLP applications that depend on the JAX-WS version included in the > JRE. It's predicated on the version of the runtime so you should be able

Re: Some suggested patches and improvements

At some level, this is the problem that is paramount on the release of JDK-9. Earlier Mark asked if the Eclipse foundation had to approve or be ready to support all of what JDK-9/Jigsaw supports before it could be released. The statement below seems to stipulate that “all Java software must be

AW: Java 9 EA 169 Webstart NoClassDefFoundError: javax/xml/ws/Service

> So I think Java Web Start is right to align with the policy for > applications launched on the command line. The difference is that in case of Webstart the Java version is controlled by the user. They are trained to install the latest Java version and keep it up-to-date. All our customers

Re: Java 9 EA 169 Webstart NoClassDefFoundError: javax/xml/ws/Service

Thanks Alan. Wouldn't it make sense to add all modules by default in Java 9 in case of Webstart and print a warning to the Webstart console the first time a future non-default module is accessed with the message that the JNLP must be extended with a --add-modules=moduleXY in Java 10? So all

What happened to ModuleClassLoader?

Re-sending since I don't see my previous post in the jigsaw-dev archives due to problems with mailing list in the past days... Forwarded Message Subject:What happened to ModuleClassLoader Date: Sun, 14 May 2017 23:11:37 +0200 From: Peter Levart

Re: Java 9 EA 169 Webstart NoClassDefFoundError: javax/xml/ws/Service

On 15/05/2017 15:10, Reto Merz wrote: Hello, It seems that Java 9 Webstart (still) does not add all modules to the class/module path. Our Webstart app is signed, requests all-permision and works with the latest Java 6, 7 and 8. With 9-ea+169 we get this error:

Re: AW: Java 9 EA 169 Webstart NoClassDefFoundError: javax/xml/ws/Service

On 16/05/2017 12:26, Reto Merz wrote: So I think Java Web Start is right to align with the policy for applications launched on the command line. The difference is that in case of Webstart the Java version is controlled by the user. They are trained to install the latest Java version and keep

Re: Some suggested patches and improvements

On 12/05/2017 14:31, David M. Lloyd wrote: : #4 seems to be working around the outcome of issue #CyclicDependences in the JSR. I also don't wish to comment on that except to say that introducing system properties to skip specified checks is highly problematic from a conformance perspective.

Re: Some suggested patches and improvements

On 12/05/2017 14:31, David M. Lloyd wrote: : There is a lot more to #5, something that will become clear when you work through all the scenarios. The JSR and spec part are minor though but I'd prefer to hold off until there is more discussion on this topic in the JSR. I'd rather not hold

Re: What happened to ModuleClassLoader?

On 16/05/2017 09:50, Peter Levart wrote: : If I remember correctly, there was a phase in jigsaw development when there was a class named ModuleClassLoader. There was although it was replaced in 2015. : Above two utility methods (defineModulesWithOneLoader and

Re: An alternative to "restricted keywords"

Thanks, Remi, for taking this to the EG list. Some collected responses: Remi: "from the user point of view, '^' looks like a hack" This is, of course, a subjective statement. I don't share this view and in years of experience with Xtext-languages (where this concept is used by default) I

Re: Some suggested patches and improvements

On 12 May 2017 at 17:31, David M. Lloyd wrote: >>> 4. Make run-time cycle checking optional >> >> My opinion is that run-time cycles are inevitable. The proposed >> solutions (refactoring to API vs Impl) is not particularly good in an >> open source context. I'm also

Re: Java 9 EA 169 Webstart NoClassDefFoundError: javax/xml/ws/Service

On 16/05/2017 09:49, Reto Merz wrote: Thanks Alan. Wouldn't it make sense to add all modules by default in Java 9 in case of Webstart and print a warning to the Webstart console the first time a future non-default module is accessed with the message that the JNLP must be extended with a

Re: Some suggested patches and improvements

On 05/16/2017 06:02 AM, Alan Bateman wrote: On 12/05/2017 14:31, David M. Lloyd wrote: : There is a lot more to #5, something that will become clear when you work through all the scenarios. The JSR and spec part are minor though but I'd prefer to hold off until there is more discussion on

Re: Some suggested patches and improvements

On 16/05/2017 19:11, Gregg Wonderly wrote: At some level, this is the problem that is paramount on the release of JDK-9. Earlier Mark asked if the Eclipse foundation had to approve or be ready to support all of what JDK-9/Jigsaw supports before it could be released. The statement below