groovy / groovy/groovy-eclipse
Allow per-project Groovy compiler version
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 681
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I know this is a limit that most probably will never be fixed in Greclipse... but I felt like it should be tracked here, as well, as it was in the old JIRA (GRECLIPSE-1196).
It would be extremely useful and "natural" if the Groovy compiler version could be set on a per-project basis, just like JDT allows for the Java compiler level.
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
The issue references Greclipse, the old JIRA item GRECLIPSE-1196, and JDT's per-project Java compiler level, but names no files or tests. Start by locating the project's compiler configuration and comparing it with JDT's project-level settings; done means each project can select its Groovy compiler version independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100