feat(cli): add Maven ecosystem resolver

[amondnet]

Summary

• Add MavenResolver class implementing EcosystemResolver interface
• Primary lookup via Maven Central Search API, fallback to POM XML for GitHub repo extraction
• Support maven:groupId:artifactId spec format (e.g. maven:com.google.guava:guava)
• Register in resolver index — getResolver('maven') now works

Refs #15

Test plan

• bun --cwd packages/cli test test/resolvers/maven.test.ts — 10 tests pass
• bun --cwd packages/cli test test/resolvers/ — all 54 resolver tests pass
• bun run --cwd packages/cli lint — clean

---

Summary by cubic

Adds a Maven resolver to the CLI so maven:groupId:artifactId specs resolve to GitHub repos, addressing #15. It uses Maven Central for versioning and prefers Search API scm.url, with fallbacks to maven-metadata.xml and the POM.

• New Features
  • Added MavenResolver implementing EcosystemResolver for maven:groupId:artifactId (e.g., maven:com.google.guava:guava) and explicit versions; registered so getResolver('maven') works.
  • Repo detection prefers Search API scm.url (default core query), then POM (<scm><url> then <url>) normalized via parseRepoUrl().
  • Version lookup uses Maven Central Search API; on failure, resolves latest via maven-metadata.xml or uses explicit version directly, then falls back to POM for repo extraction. Returns ref as v{version} with {version} fallback.

^{Written for commit 078e47e. Summary will update on new commits.}

Verification Checklist

• bun --cwd packages/cli test test/resolvers/maven.test.ts — 18 tests pass
• bun --cwd packages/cli test test/resolvers/index.test.ts — 5 tests pass
• bun --cwd packages/cli test test/resolvers/ — all 62 resolver tests pass
• bun run --cwd packages/cli lint — clean

[codecov]

Codecov Report

❌ Patch coverage is 99.24242% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
packages/cli/src/resolvers/maven.ts	99.23%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[cloudflare-workers-and-pages]

Deploying ask-registry with    Cloudflare Pages

Latest commit:	078e47e
Status:	⚡️  Build in progress...

View logs

[cubic-dev-ai]

0 issues found across 3 files (changes from recent commits).

_{Requires human review: This is a new feature implementation adding a Maven ecosystem resolver. It contains non-trivial logic including API interactions and regex-based XML parsing that requires human review.}

[cubic-dev-ai]

No issues found across 8 files

_{Requires human review: New feature adding a non-trivial ecosystem resolver. While isolated, it includes complex logic like regex-based XML parsing and external API integration that requires human review.}

Architecture diagram

sequenceDiagram
    participant CLI as CLI Core
    participant Index as Resolver Index
    participant Maven as NEW: MavenResolver
    participant SearchAPI as Maven Central Search API
    participant MavenRepo as Maven Central Repository (repo1)

    Note over CLI, MavenRepo: maven:groupId:artifactId Resolution Flow

    CLI->>Index: CHANGED: getResolver('maven')
    Index-->>CLI: MavenResolver instance

    CLI->>Maven: NEW: resolve(name, version)
    Maven->>Maven: Parse "groupId:artifactId"

    rect rgb(240, 240, 240)
    Note right of Maven: Version Resolution
    alt version is 'latest'
        Maven->>SearchAPI: GET /solrsearch?q=g:G+AND+a:A
        alt Search API Success
            SearchAPI-->>Maven: Latest version + scmUrl
        else Search API Failure
            Maven->>MavenRepo: NEW: GET /.../maven-metadata.xml
            MavenRepo-->>Maven: XML with <release> tag
        end
    else explicit version provided
        Maven->>SearchAPI: GET /solrsearch?q=...&v=V (Try for scmUrl)
        SearchAPI-->>Maven: Version metadata
    end
    end

    rect rgb(240, 240, 240)
    Note right of Maven: Repository Mapping (Priority Flow)
    alt scmUrl found in Search API docs
        Maven->>Maven: parseRepoUrl(scmUrl)
    else scmUrl missing or invalid
        Maven->>MavenRepo: NEW: GET /.../{artifactId}-{version}.pom
        MavenRepo-->>Maven: POM XML content
        Maven->>Maven: NEW: extractRepoFromPom() (Regex <scm> or <url>)
    end
    end

    alt GitHub URL Resolved
        Maven-->>CLI: ResolveResult { repo, ref: "v{v}", resolvedVersion: "{v}" }
    else No GitHub URL found
        Maven-->>CLI: Throw Error (Suggest 'owner/repo' format)
    end

Loading