-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add option to fork for JDK9 support #64
Comments
Note that a workaround is to add the modules to |
Hi, thank for feedbacks Interesting topic ....probably the issue could be solved adding a new ad-hoc argument what do you think about ? |
I'm not sure what you mean by ad hoc argument. Could you elaborate? |
I mean a new configuration tag in your case fork ( However i suppose that you for module mean a jar, if it is so, have you tried to add it as plugin and/or project dependency ? |
No what I mean in the JDK 9 sense are modules available on the module path like e.g. java.xml.bind. |
Hi Plugin now read If you have chance to test it, I really appreciate that Thanks in advance |
released in version |
I just ran into an issue with this plugin and JDK 9. One of my annotation processors uses a module that isn't visible by default, thus I have to add the module via command line flags. Apparently the module is not picked up by javac if it's running in the same JVM so creating a forked javac would solve the issue.
Can you provide a option similar to what other plugins provide?
The text was updated successfully, but these errors were encountered: