gradle / gradle/gradle-plugin-analyzer
Detect tasks with JavaBean properties
Open
- Dominant language
- Java
- Stars
- 9
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Tasks should only declare lazy properties.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the bytecode-analysis entry point for Gradle tasks and the existing property-detection logic. Define completion as detecting task properties that are not lazy and reporting them consistently, but the issue does not identify files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100