groovy / groovy/groovy-eclipse
Add warning for star import not found on project classpath
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 681
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Consider the following:
import foo.bar.*
import foo.bar.Baz.*
...
When building, warning/error should be produced for each import statement if package "foo.bar" is not part of classpath. Each of the other 3 types of imports produce errors for non-found types. JDT tools provide a problem marker in Java for these cases.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how Groovy-Eclipse handles the four import forms and compare the requested behavior with JDT's Java problem markers. Done means producing a warning or error for each star import whose package or type is not found on the project classpath.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100