Remove Groovy-ness in Visual Studio metadata generation
Open
- Dominant language
- No language data
- Stars
- 94
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Some of the internal stuff for Visual Studio metadata generation (i.e. stuff in `org.gradle.ide.visualstudio.tasks.internal`) is implemented in Groovy. We should look into replacing this with Java.
Contributor guide
Research direction
Start by inspecting the internal Visual Studio metadata generation code under org.gradle.ide.visualstudio.tasks.internal and identify which parts are implemented in Groovy. Determine the scope of replacing those parts with Java; done means the internal implementation no longer relies on Groovy while preserving metadata generation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100