JetBrains / JetBrains/junie-guidelines
Add guidelines for how to structure Java code
Open
- Dominant language
- No language data
- Stars
- 425
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Describe the recommended package structure for organizing Java code.
Consider:
- package-by-feature
- Clean/Hexagonal Architecture
Add a detailed package structure for a sample multi-module Java application.
Contributor guide
Research direction
No target files or tests are named. Start by reviewing the repository's existing documentation structure, then define the sample multi-module Java application's package layout and explain package-by-feature alongside Clean/Hexagonal Architecture. Done means the guidelines contain a detailed, understandable structure covering the requested approaches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100