Improve Maven repo search revelance

[nickzhums]

Per survey feedback, when adding dependency in Maven and Gradle, improve the overall smartness and relevance

[github-actions]

Hi @nickzhums, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggestions to improve Maven and Gradle dependency search relevance:

• Retrieve artifact metadata in real time from Maven Central (and Gradle Plugin Portal) via their REST APIs instead of relying solely on the local cache:
  • Maven Central Classic API: https://search.maven.org/classic/#api
  • Gradle Plugin Portal REST API: https://plugins.gradle.org/docs/portal#rest-api
• Enhance query “smartness” by:
  • Tokenizing and fuzzy-matching user input against groupId, artifactId, and description fields.
  • Ranking results based on download count, recent update time, and exact vs. partial match.
• Cache popular queries locally for faster response while still validating freshness against the remote API.

duplicateUrls:

• Auto complete for dependencies for pom.xml vscode-maven#195 (comment)

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!