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]

Re: Closing issues in JIRA

Hi, I have checked that I'm unable to do that on Maven Assembly plugin but on others for example maven-jar-plugin I'm allowed to do so... Kind regards Karl Heinz Marbaise On 17/06/17 13:18, Karl Heinz Marbaise wrote: Hi, it looks at the moment that I'm unable to close (closed as duplicate

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

Closing issues in JIRA

Hi, it looks at the moment that I'm unable to close (closed as duplicate etc.) an issue ? is this a general problem for others as well or only for me? Any ideas? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail:

Re: Closing issues in JIRA

Hi, created an INFRA Ticket for that issue. https://issues.apache.org/jira/browse/INFRA-14380 Kind regards Karl Heinz Marbaise On 17/06/17 13:21, Karl Heinz Marbaise wrote: Hi, I have checked that I'm unable to do that on Maven Assembly plugin but on others for example maven-jar-plugin I'm

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

[RESULT] [VOTE] Release Apache Maven Shared Component: Maven Shared Utils Version 3.2.0

Hi, The vote has passed with the following result: +1 : Hervé Boutemy, Olivier Lamy, Karl Heinz Marbaise PMC quorum: reqched. I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise - To

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

[ANN] Apache Maven Shared Component: Maven Shared Utils Version 3.2.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Shared Utils Version 3.2.0 https://maven.apache.org/shared/maven-shared-utils/ You should specify the version in your project: org.apache.maven.shared maven-shared-utils 3.2.0 You

Re: New Branch (report real sys props of forked JVM) SUREFIRE-1360

I have fixed https://issues.apache.org/jira/browse/SUREFIRE-1302 in branch https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=b9034a3bbb32a27a2d7b66e4d516c2dac61fce29 Tested and made debugging. Forked VM is killed immediately. On Wed, Apr 26, 2017 at 3:38 AM, Tibor Digana