micronaut-projects / micronaut-projects/micronaut-data

Development Improvements

Open
#806 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: question
Dominant language
Java
Stars
482
Forks
229
Avg merge
1d 7h
Merged PRs (30d)
32

Description

@graemerocher

I have difficulties with Intellij IDEA. I think maybe I don't have enough experience with Gradle but seems there is a need for documentation for this as well. What I want to do is just adding a test case and changing necessary things in the project without rebuild of IDEA for each time. I think having a documentation about will be super good. I will add my points which can be improved.

1. In the Micronaut Core documentation there is some section about adding annotation processors to class path for testing. Even if I add, I have to rebuild entire project in case a change of a code change. What is the proper way for development? I have some problems with Gradle Dameons too.
2. I think it is very helpful to see generated intermediate generated classes. I usually open target folders for generated classes. Is there an easy way for it?
3. How can I debug annotation processors? Since they are triggered at build time, is it possible to put a breakpoint and follow generation?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Micronaut Core documentation section on adding annotation processors for testing, then review the IntelliJ IDEA and Gradle development concerns listed in this issue. Document the proper workflow for changing code and tests without rebuilding the IDE, viewing generated classes, and debugging annotation processors; done means each question has a clear, verified answer.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
developer-experience, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.