[Java][E38] Resolve Maven Central packages by artifactId at any reactor depth
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, ci-cd, release
Research direction
Read maven-central/action.yml and maven-central/validate_publish.py first, tracing the package input through the current mvn -pl invocation and flat path checks. Exercise nested-reactor resolution without a real publish, verify empty-list and rejection behavior plus matching action/validator semantics, and confirm the immutable action SHA requirement before caller updates.
Written by the indexing model from the issue text.
Description
Parent and sequencing
Related engine design epic: InditexTech/internal-ops#55. This action change must land and expose an immutable release before any independent Java monorepo caller can adopt it; caller re-pins then follow through governance.
Problem
maven-central currently interprets packages[] as flat directories and invokes Maven with path-shaped -pl values. The Java governance contract is converging on Maven artifactId, and nested reactors cannot be represented safely by the current action.
This is not blocking the current karatetools/scs-outbox migration while both remain release.strategy: locked-step and pass an empty package list. It becomes blocking for the first independent monorepo or any caller that forwards artifact IDs.
Acceptance criteria
- Resolve each non-empty package through Maven reactor identity (
:<artifactId>) at arbitrary module depth. - Accept the empty list required by
locked-stepwithout discovering or publishing extra modules. - Reject unknown, duplicate, aggregate-only, fixture, test, or unintended classifier artifacts.
- Keep action and
validate_publish.pysemantics identical. - Exercise nested-reactor behavior without a real publish, then perform any required registry proof only on an authorized
testing/canary. - Release an immutable action SHA before updating archetype callers.
Evidence
.migration/bugs.md, E38.- Current action:
maven-central/action.ymlpackage input andmvn -plinvocation. - Current validator:
maven-central/validate_publish.pyflat path checks.
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- Avg merge
- 2h 23m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
fuzz fuzz-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Switch to ruffOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Qiskit/qiskit-aer#2533 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
etesync/etesync-dav#376 ·