Error on JDK10: -Xbootclasspath/p is no longer a supported option.

[eolivelli]

I get the same error even on JDK10

-Xbootclasspath/p is no longer a supported option.

Is there any workaround ?

Unfortunately -XX:+IgnoreUnrecognizedVMOptions does not help

I can send a patch, like if Java Version > 10 then do not add Xbootclasspath

[alankila]

Since the release of jdk 11, wsimport is no longer supplied with the JDK distribution. This broke my workaround for this issue in JDK versions 9 and 10, where I specified <executable>${java.home}/bin/wsimport</executable> into the pom.xml file to override the inclusion of the no-longer working option -Xbootclasspath/p into the command line. As far as I can tell, there is no long any way to use jaxws-maven-plugin on jdk 11 until the issue is fixed, perhaps in a new release.

[theit]

Can you have a look at my pull request #71? It contains fixes for invocation under Java 9-11, and at least on my machine it's not necessary anymore to specify an executable as a workaround for Java >=9.

[hugo-ma-alves]

Can you have a look at my pull request #71? It contains fixes for invocation under Java 9-11, and at least on my machine it's not necessary anymore to specify an executable as a workaround for Java >=9.

Thanks for the fix I tried your version on our project and it works on java 11. I added some more details about our setup on the PR comments page.

[theit]

Great to hear. Now let's wait for the project maintainers/owners what they think about the PR... ;-)

[gmcouto]

Yeah, I'm still waiting for these

[HashRaygoza]

Any news about this?

[theit]

Is this still an issue with version 2.6 of this plugin that was released recently?

[adiesner]

Is this still an issue with version 2.6 of this plugin that was released recently?

Upgrading from 2.5 to 2.6 fixed the issue for me.

            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>jaxws-maven-plugin</artifactId>
                <version>2.6</version>
 ...

[niklaj]

Can you have a look at my pull request #71? It contains fixes for invocation under Java 9-11, and at least on my machine it's not necessary anymore to specify an executable as a workaround for Java >=9.

The proposed fix does not solve the problem if the toolchains plugin is used as it is checking the module status for the current jvm (which might be java 8) and not for the toolchain jvm that might be java 9 or later.

[pdudits]

I've also hit same issue like @niklaj did, but since I think it is more specific than "Doesn't work on JDK 10", I filed new issue #94.