Add a `maven` skill: agents install Debian's `maven` package, which can't load plugins built for Java 17+

Open Beginner friendly
#963 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@sumitvairagar is already working on this.

Since Nov 19, 2026.

  • #964 by @sumitvairagar — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
debian, java
Domain
tooling

Research direction

Use the existing uv and npm skills as templates, then read the skill authoring and catalog generation instructions referenced in the issue. Add skills/maven/SKILL.md, README.md, its plugin manifest and marketplace entry; document wrapper preference, verified upstream Maven installation, JDK setup, common commands, and sandbox failures. Regenerate the catalogs with the named repository commands and check that the documented repro and acceptance criteria are covered.

Written by the indexing model from the issue text.

Description

priority:medium ready-for-dev

The registry has environment skills for uv, npm and deno, but nothing for Maven. In the Agent Canvas image (Debian 13), an agent that needs Maven runs apt-get install maven, and that package breaks on modern Maven plugins.

Problem. Debian 13's maven 3.9.9 package replaces Maven's bundled Eclipse Sisu 0.9.0.M3 with the system libsisu 0.3.5. Sisu 0.3.5 can't load plugins compiled for Java 17 or newer, for example io.github.ascopes:protobuf-maven-plugin 5.x. The build then fails with Unable to load the mojo 'generate' and Guice/NullInjectedIntoNonNullable. mvn -v shows 3.9.9 either way, so nothing hints at the cause. ascopes/protobuf-maven-plugin#853 describes the same mechanism with old Sisu versions.

Repro (in ghcr.io/openhands/agent-canvas:latest, with a one-module project using protobuf-maven-plugin 5.1.11):

  • Debian maven 3.9.9: fails with the error above.
  • Upstream Apache Maven 3.9.9 (same version number, from archive.apache.org): BUILD SUCCESS.

I hit this building a2aproject/a2a-java in Agent Canvas.

Proposal. A small skills/maven environment skill, in the style of uv and npm:

  • prefer ./mvnw
  • otherwise detect the Debian package and install upstream Maven, with checksum verification
  • the multi-module flags (-pl, -am), running a single test, and offline mode
  • a short table of common sandbox failures

I've drafted it and tested it end to end in Agent Canvas with no JDK or Maven installed. The agent picked up the skill, avoided the Debian package and built the project on the first try. Happy to open a PR once this is triaged.


OpenHands AI triage

The following comments and acceptance criteria were added by the OpenHands AI agent.

Triage

Verified against the repository at main: the registry has no maven skill and no duplicate issue. Sibling environment skills (uv, deno, npm, swift-linux) follow one structure - skills/<name>/SKILL.md with AgentSkills frontmatter and keyword triggers, a required non-empty README.md, a .plugin/plugin.json manifest with .claude-plugin/.codex-plugin vendor symlinks, and a marketplaces/openhands-extensions.json entry with category environment - with derived artifacts (skills/index.js, the README auto-generated catalog section) regenerated by npm run build:skills and scripts/sync_extensions.py, which CI checks. The issue matches that pattern, and the author reports having tested the proposed content end to end in Agent Canvas.

Scope: one new skills/maven environment skill (SKILL.md + README.md + plugin manifest) and its marketplace entry, with derived catalogs regenerated using the existing commands. Content covers: preferring the project ./mvnw wrapper; otherwise detecting Debian's maven package and installing upstream Apache Maven with SHA-512 checksum verification instead of apt-get install maven; multi-module flags (-pl, -am), single-test runs, and offline mode; and a short table of common sandbox failures including the Unable to load the mojo / Guice/NullInjectedIntoNonNullable failure mode from this issue.

Non-goals: no changes to existing skills or plugins; no executable plugin code, hooks, or commands/; no CI workflow changes; no changes to the Agent Canvas base image; no system-wide purging of Debian's maven package; no integration/automation/app catalog changes.

Priority medium: a first-person user report of a reproduced failure in the actual Agent Canvas workflow (building a2aproject/a2a-java in ghcr.io/openhands/agent-canvas:latest), with a concrete repro and an author-tested fix. Not high: a single report with no broader support or production evidence on record.

Acceptance Criteria
  • A new skills/maven/ directory contains SKILL.md with AgentSkills frontmatter declaring name: maven, a description consistent with the marketplace entry, and keyword triggers including maven; it loads via the SDK (the skill-loading test in tests/test_sdk_loading.py passes).
  • skills/maven/README.md exists, is non-empty, and describes the same scope and triggers as SKILL.md (tests/test_skills_have_readme.py passes).
  • SKILL.md directs the agent to build with the project's ./mvnw wrapper whenever it exists, without installing any global Maven in that case.
  • When no wrapper exists, SKILL.md documents a Debian-package detection step and an upstream Apache Maven install that downloads the binary tarball from Apache's archive and verifies the published SHA-512 checksum before use; it does not instruct apt-get install maven and states why the Debian package is avoided.
  • The documented steps include obtaining a JDK, so that in a clean Debian 13 environment with neither Maven nor a JDK installed, following SKILL.md end to end results in mvn -v reporting the upstream Apache Maven distribution and a successful build of a one-module Maven project using a Java 17+-targeted plugin (e.g., io.github.ascopes:protobuf-maven-plugin 5.1.11), matching the issue's repro.
  • SKILL.md documents multi-module builds (-pl, -am), running a single test, and offline mode.
  • SKILL.md includes a short table of common sandbox failures with observable symptoms and fixes, including the Unable to load the mojo / Guice/NullInjectedIntoNonNullable failure mode described in this issue.
  • marketplaces/openhands-extensions.json gains a maven entry with source ./skills/maven and category environment; skills/maven/.plugin/plugin.json mirrors it, and the .claude-plugin/.codex-plugin vendor symlinks match sibling skills.
  • Derived artifacts are regenerated only with the repository's existing commands: npm run build:skills for skills/index.js and python scripts/sync_extensions.py for the README auto-generated catalog section; python scripts/sync_extensions.py --check exits 0.
  • The new content contains no secrets, private paths, or company-specific URLs, and no em dash (U+2014) characters in the SKILL.md description, SKILL.md content, or marketplace entry, per repository authoring rules.
  • Automated validation passes on the changed tree: npm run build:skills, python scripts/sync_extensions.py --check, and uv sync --group test followed by uv run pytest -q all exit 0.
Dominant language
Python
Stars
184
Forks
137
Avg merge
1d 16h
Merged PRs (30d)
60

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/extensions

All issues in OpenHands/extensions

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.