Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

On Mon, 19 Jun 2017 13:21:22 +0200, Enrico Olivelli wrote: Karl, I am getting this error using maven site plugin 3.6 and jdk 9-ea+174 java.lang.reflect.InaccessibleObjectException: Unable to make protected final java.lang.Class

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

Karl, I am getting this error using maven site plugin 3.6 and jdk 9-ea+174 java.lang.reflect.InaccessibleObjectException: Unable to make protected final java.lang.Class java.lang.ClassLoader.findLoadedClass(java.lang.String) accessible: module java.base does not "opens java.lang" to unnamed

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

Il dom 18 giu 2017, 09:38 Tibor Digana ha scritto: > @Enrico > What "--add-modules ALL-SYSTEM" really does ? > For me it would be maybe a handy hack but for you it would be just a hack > anyway as it first seems. Strong encapsulation in Java9 can be openly > passed

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

@Enrico What "--add-modules ALL-SYSTEM" really does ? For me it would be maybe a handy hack but for you it would be just a hack anyway as it first seems. Strong encapsulation in Java9 can be openly passed by. For instance in Surefire we extend UrlClassLoader and I need to access entire Java API

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

+1, fully agree with Guillaume There's no real need to make a plugin modular: it won't become a dependency and the dependency management as done by Maven is strong enough to have a stable plugin (i.e no need to add requires-statements). In case of experiment if you want to add a module

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

Il sab 17 giu 2017, 16:40 Karl Heinz Marbaise ha scritto: > Hi, > > If i correctly understand the error message it would help having a > module-info.java with a proper name and a require clause to say that we > need access to java.io.File... > Currently we have a unnamed

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

Hi, If i correctly understand the error message it would help having a module-info.java with a proper name and a require clause to say that we need access to java.io.File... Currently we have a unnamed module which prevents such access... Kind regards Karl Heinz Marbaise On 17/06/17 16:31,

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

Karl, I think that the problem is tha code is trying to access internals of java.io.File. No module descriptor can help. I think you should run with -X, get the stacktrace of the exception and then we need to avoid that reflective call. In the meantime you can use the famous big kill switch. Hope

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

Hi, There was a link to Stephen Colebourne's blog about naming modules: http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html. So what about "org.apache.maven.plugins.site" for the module name? But I don't think it is necessary to make the plugin modular. The error means that code

JDK9: Jigsaw Problem with maven-site-plugin 3.6

Hi, currently I'm a bit on testing JDK 9 EA+174..and found the following issue: [INFO] [INFO] <<< maven-plugin-plugin:3.4:report < process-classes @ maven-install-plugin <<< [INFO] [INFO] 'process-classes' forked phase execution for maven-plugin-plugin:report report preparation done [INFO]