-
Notifications
You must be signed in to change notification settings - Fork 193
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 quick fix(es) for modular project classpath/modulepath problems #1059
Comments
eric-milles
added a commit
that referenced
this issue
Mar 13, 2020
eric-milles
added a commit
that referenced
this issue
Mar 18, 2020
eric-milles
added a commit
that referenced
this issue
Mar 23, 2020
eric-milles
changed the title
Add quick fix(es) for fixing modular project classpath/modulepath problems
Add quick fix(es) for modular project classpath/modulepath problems
Mar 24, 2020
eric-milles
added a commit
that referenced
this issue
Mar 24, 2020
eric-milles
added a commit
that referenced
this issue
Mar 24, 2020
eric-milles
added a commit
that referenced
this issue
Mar 26, 2020
- was offset 0, length 1 which results in underline for first character #1059
eric-milles
added a commit
that referenced
this issue
Mar 26, 2020
eric-milles
added a commit
that referenced
this issue
Mar 30, 2020
eric-milles
added a commit
that referenced
this issue
Mar 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow up from #1045. When the Groovy runtime classes are not available on the classpath, there is a quick fix offered to add the Groovy Libraries classpath container.
However, when the Groovy runtime classes are available, there is no quick fix offered to add a requires statement to the module-info.java of a modular project. Only the cryptic quick fix "Configure build path..." is available.
The Java editor offers additional quick fixes for a modular project to assist the user in fixing modulepath problems.
The text was updated successfully, but these errors were encountered: