-
Notifications
You must be signed in to change notification settings - Fork 39
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
Asciidoclet fails with "invalid flag error" on Java 10 #81
Comments
Agreed, we should just move to the new API as you state in option 1 - option 2 is working in the wrong direction. |
I think I might have a similar issue with JDK 11 and the It would be nice if we could find a solution as the Hibernate ORM 6 javadoc is now heavily relying on Asciidoclet and we still have a lot of legacy javadoc that needs some fixing thus the use of the |
I'm also running into this on Java 11. Specifically I'm seeing that the |
Looks like maybe the "invalid flags" can be worked around by setting
With that set, I now get a |
When I try to run the current Asciidoclet 1.5.5-SNAPSHOT with Java 10 via the Gradle javadoc task I get the following error:
This is because the old "Standard Doclet" was removed in Java 10 (http://www.oracle.com/technetwork/java/javase/10-relnote-issues-4108729.html#JDK-8177511) and Asciidoclet runs as a preprocessor that in-turn calls the Standard Doclet.
I'm not sure if this is worth trying to fix separately from Issue #71. In other words there are two approaches to resolving this:
So, it seems to me like #71 is probably the best solution. But there may be other solutions and we need to track this specific issue that we are seeing under Java 10+.
The text was updated successfully, but these errors were encountered: