Why groovy?
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 603
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
Just a question - why groovy and not java? I would rather use 8-11 java with all the stream-lambda-vars etc. And also smart completion in Intellij. And pitest mutation coverage and lots of other things...
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 reading issue #270 and the repository description to understand the question about Groovy versus Java in Gradle-based Python builds. Done would require a maintainer decision and an explanation of the choice, but the issue names no file, test, or documentation location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- build-system
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100