-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java 11 support #20
Comments
I've run the latest version of Enunciate with Java 11 and it works fine with the simple use cases I have. That indicates that the changes need to be included in the gradle wrapper. Yes? |
Sorry for the delay in answering @stoicflame , life interfered. But when I look here: The module does use the jaxb-api classes.
So I am pretty sure the enunciate-jaxb should depend on "javax.xml.bind:jaxb-api:2.3.1" (or whichever version it is built with). Similar for the enunciate-jaxws module which should depend on "javax.jws:javax.jws-api:1.1" (due to its import of javax.jws.WebService). I could of course add the dependencies to the gradle plugin. Not sure why this is not an issue with Maven?! Could it be because the Gradle plugin depends on enunciate-top? Should it be enunciate-parent instead? |
Okay, I've opened stoicflame/enunciate#926 to track the issue. |
Hi @stoicflame ... I have the same problem with the enunciate, how you resolved the problem? which dependencies you added? thank a lot for your help |
@piterrivero did you read the original problem text? It contains the workaround... |
@jskovjyskebankdk yes I did it! but I'm using maven, so I added these two dependencies javax.jws:javax.jws-api:1.1 and javax.xml.bind:jaxb-api:2.3.1 but however still I have the problem. Thank you! |
@piterrivero, if you're using Maven, you should probably open up a separate issue at enunciate/issues. You'll probably need to provide a way to reproduce the problem as I can't see it on my end. |
In building my project with enunciate on JDK 11, I still get these warnings from maven: Which tells me the enunciate plugin is still pulling in these old dependencies somewhere in its dependency tree. I don't have those anywhere in my code base. (Why oracle published those with broken poms is neither her nor there) While maven does allow you to add or override versions of dependencies for a plugin, it appears that they never added support for excluding dependencies: https://issues.apache.org/jira/browse/MNG-2163 It doesn't currently break my build on JDK 11, but I think its something that needs to be fixed in the enunciate plugin itself if we want to fully get rid of these old xml jar files. I did a maven dependency:tree on the 2.11.1 tag, I found a few refs:
Some are like this, you will likely have to ban them in your dependency tree unless the upstream projects have new versions that finally stopped using them:
|
Also running into this problem with openjdk 11, specifically Amazon's corretto: Using enunciate 2.11.1
Adding these(as seen here: stoicflame/enunciate#926 (comment)) does not help:
|
To use enunciate with java 11, I had to use the old form of plugin activation, specifying some additional jars:
This was with enunciate modules docs, jaxrs, and jaxbs enabled.
The gradle wrapper should probably be changed to include those dependencies.
Or maybe the maven module com.webcohesion.enunciate:enunciate-top should be?
Do you know, @stoicflame, if something similar is required for Maven and java11?
The text was updated successfully, but these errors were encountered: