Maven artefact version suggestion in build.gradle files
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Description
It would be great if Gradle/Groovy could provide the same when on a line with a dependency, like:
`testImplementation 'io.micronaut.test:micronaut-test-junit5:3.1.1'`
### Use case/motivation
MAVEN projects have a very useful artefact version suggestion when trying to enter the `version` element inside the pom.xml.
Saves time to figure out the latest version of an artifact - given that NB already provides a maven index.
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow the Apache Software Foundation's [Code of Conduct](https://www.apache.org/foundation/policies/conduct.html)
Contributor guide
Research direction
Start by tracing the existing Maven pom.xml artifact-version suggestion and the Gradle/Groovy completion path for dependency lines in build.gradle files. Compare how the Maven index is used for pom.xml and determine the corresponding Gradle entry point. Done means a dependency such as testImplementation 'io.micronaut.test:micronaut-test-junit5:3.1.1' offers artifact version suggestions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100