apache / apache/maven

[MNG-6211] Improve relocation message

Open
#7,237 1 comment 0 reactions 0 assignees View on GitHub
enhancement priority:major
Dominant language
Java
Stars
5.3k
Forks
3.1k
Avg merge
21h 11m
Merged PRs (30d)
312

Description

**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** opened **[MNG-6211](https://issues.apache.org/jira/browse/MNG-6211?redirect=false)** and commented

Consider the following setup:

```
A:1.0 -> B:1.1
C:1.1 -> B:1.0
B:1.4 >>> D:1.4
My -> A:1.0, B:1.3, C:1.1
```

When upgrading My B to 1.4, I'll get a warning about the relocation. But when I replace B:1.4 with D:1.4, B:1.1 will be pulled in because it is a transitive dependency of A and because D is not aware being the relocation of B.

In this case the relocation should be INFO, because following the instruction will have an unpleasant surprise.

---
No further details from [MNG-6211](https://issues.apache.org/jira/browse/MNG-6211?redirect=false)

Contributor guide

Open the contributing guide

Research direction

Start by tracing Maven's relocation warning and dependency-resolution behavior for the A, B, C, and D versions described in the issue. The payload names no source files or tests, so identify the relevant entry point and add coverage showing when a relocation should be reported at INFO; done means the replacement does not produce the described transitive-dependency surprise.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.