fix: use HTTPS for Maven Central version queries

[felipeofdev-ai]

Summary

• Switch Maven Central Solr search queries from http://search.maven.org to https://search.maven.org.
• Clarify README: HTTPS for Maven Central; JCenter is legacy/shutdown for publishing.

Why

Plain HTTP to Maven Central is outdated and can fail under strict network policies. Google Maven / JitPack already used HTTPS.

Test plan

• Existing unit tests that fake Maven Central responses still pass (URL host unused by FakeApi)
• Manual: detector can still resolve a known Maven Central coordinate when network is available

---

— Felipe Fernandes · Systems & Agentic AI Engineer
https://github.com/felipeofdev-ai · https://felipeofdev-ai.github.io/

[Copilot]

Pull request overview

Updates Maven Central version lookup to use HTTPS for Solr search queries, aligning with modern network/security requirements and avoiding failures under strict HTTP-only restrictions.

Changes:

• Switch Maven Central Solr endpoint from http://search.maven.org to https://search.maven.org.
• Update README to clarify HTTPS usage for Maven Central and note JCenter/Bintray’s legacy status.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
README.md	Documents HTTPS usage for Maven Central and clarifies repository status guidance.
lintversioncheck/src/main/java/com/picpay/gradlelint/versioncheck/repositories/MavenCentral.kt	Updates the Maven Central query base URL to HTTPS.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.