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 that helps
I will be happy to check the problem next week and help if possible


Enrico

Il sab 17 giu 2017, 15:54 Karl Heinz Marbaise <khmarba...@gmx.de> ha
scritto:

> 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] configuring report plugin
> org.apache.maven.plugins:maven-invoker-plugin:2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 14.810 s
> [INFO] Finished at: 2017-06-17T15:47:38+02:00
> [INFO] Final Memory: 57M/256M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on
> project maven-install-plugin: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to
> make private java.io.File(java.lang.String,java.io.File) accessible:
> module java.base does not "opens java.io" to unnamed module @44b002c9 ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
>
> So based on what I understood at the moment is that the
> maven-site-plugin needs to have a module-info.java file....
>
> The first thing which came into my mind was how-to name the module?
>
> module org.apache.maven.plugins.maven.site.plugin {
>    requires java.io;
>    requires java.base;
> }
>
> Do we have any kind of general naming convention for the plugins?
>
> Kind regards
> Karl Heinz Marbaise
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --


-- Enrico Olivelli

Reply via email to