groovy / groovy/groovy-eclipse
lombok.config ignored when using groovy-eclipse-compiler
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 681
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I'm not entirely sure if this is an issue or something with my settings, but when following the guidance here on getting groovy-eclipse-compiler to work with lombok, my lombok.config file seems to get ignored (I've tried moving it around to no avail).
For example, if I add lombok.log.fieldName = LOG to the lombok.config and update my source code accordingly, everything will work fine in eclipse but running mvn clean compile will lead to the following error:
[ERROR] LOG.debug("test");
[ERROR] ^^^
[ERROR] LOG cannot be resolved
using maven-compiler-plugin without the groovy-eclipse-compiler seems to work fine.
what could be going on here?
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 reproducing the issue with the project Lombok guidance linked in the report, using groovy-eclipse-compiler and mvn clean compile. Compare the failing Maven build with the working Eclipse setup, focusing on how lombok.config and lombok.log.fieldName = LOG are discovered. Done means the Maven compilation recognizes the configured LOG field as the Eclipse build does.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100