Re: JAR searched on the classpath instead of the module path in Build #156

2017-03-19 Thread Alan Bateman
On 18/03/2017 19:17, Paul Bakker wrote: Thanks for the quick fix! When will a new build available? I need this fix for my Devoxx presentation Tuesday, or come up with a different plan to work around it. The builds on jdk9.java.net/jigsaw are published daily (as needed) but I think it's only Mo

Re: JAR searched on the classpath instead of the module path in Build #156

2017-03-18 Thread Paul Bakker
Thanks for the quick fix! When will a new build available? I need this fix for my Devoxx presentation Tuesday, or come up with a different plan to work around it. Paul On Sat, Mar 18, 2017 at 1:09 AM, Alan Bateman wrote: > On 18/03/2017 07:09, Paul Bakker wrote: > > Following up on my earlier m

Re: JAR searched on the classpath instead of the module path in Build #156

2017-03-18 Thread Alan Bateman
On 18/03/2017 07:09, Paul Bakker wrote: Following up on my earlier message, I think I found a bug in jdk.internal.loader.BuiltinClassLoader. When a resource is loaded from a package that does not contain classes in an automatic module, the loading works fine. When the resource is loaded from a p

Re: JAR searched on the classpath instead of the module path in Build #156

2017-03-18 Thread Paul Bakker
Following up on my earlier message, I think I found a bug in jdk.internal.loader.BuiltinClassLoader. When a resource is loaded from a package that does not contain classes in an automatic module, the loading works fine. When the resource is loaded from a package that does contain classes, the loadi

Re: JAR searched on the classpath instead of the module path in Build #156

2017-03-17 Thread Paul Bakker
Hi Alan, I'm upgrading my "Migrating to Java 9 Modules" talk to the latest build and run into the same problem with build 9-ea+160-jigsaw-nightly-h6207-20170316. Hibernate-core is an automatic-module. This JAR contains the xsd file that can't be loaded. The Hibernate code does the following: pub

Re: JAR searched on the classpath instead of the module path in Build #156

2017-02-13 Thread Sanne Grinovero
Hi Alexandru, please be aware that Hibernate to support Jigsaw is a work in progress. We had some successful builds (including test runs) some months ago, but we have yet to catch up on recent changes in OpenJDK. Progress for each Hibernate project can be monitored here: - http://ci.hibernate.or

Re: JAR searched on the classpath instead of the module path in Build #156

2017-02-12 Thread Alan Bateman
On 12/02/2017 13:29, Alexandru Jecan wrote: : I compile my application, create the modular JAR and then at runtime I get the error: Caused by: org.hibernate.boot.jaxb.internal.stax.XmlInfrastructureException: Unable to locate schema [org/hibernate/jpa/orm_2_0.xsd] via classpath Co

JAR searched on the classpath instead of the module path in Build #156

2017-02-12 Thread Alexandru Jecan
Hello Jigsaw team, I have the following problem in Jigsaw build #156: I moved the hibernate-core.jar to automatic modules by putting it on the module path. I also have a classpath that does not contain this JAR. In my module-info.java I require it using “requires hibernate.core”. I co