apache / apache/maven-resolver

[MRESOLVER-693] Deprecate mvn4 supplier module

Open
#1,449 2 comments 0 reactions 0 assignees View on GitHub
maintenance priority:major
Dominant language
Java
Stars
152
Forks
160
Avg merge
1d 4h
Merged PRs (30d)
49

Description

**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MRESOLVER-693](https://issues.apache.org/jira/browse/MRESOLVER-693?redirect=false)** and commented

Once new "standalone Maven API" module materializes and becomes released (lands on Maven Central) the supplier-mvn4 should be deprecated with a message pointing at new "standalone API" artifacts.

Supplier mvn4 anyway used Maven4 in "maven 3 way": via maven-resolver-supplier that IS in Maven 4 compat.

---

**Issue Links:**
- [MNG-8637](https://issues.apache.org/jira/browse/MNG-8637) Pull out "Standalone API" from UTs
(_**"requires"**_)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the linked MNG-8637 issue and confirming when the standalone Maven API artifacts are released to Maven Central. Then locate the supplier-mvn4 module and its use through maven-resolver-supplier. Done means supplier-mvn4 is deprecated with a message pointing to the standalone API artifacts.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.