You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2025/04/03 18:54:00 UTC
[jira] [Updated] (MNG-8616) Maven should be smarter with extension conflicts
[ https://issues.apache.org/jira/browse/MNG-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated MNG-8616:
---------------------------------
Issue Type: New Feature (was: Task)
> Maven should be smarter with extension conflicts
> ------------------------------------------------
>
> Key: MNG-8616
> URL: https://issues.apache.org/jira/browse/MNG-8616
> Project: Maven
> Issue Type: New Feature
> Affects Versions: 4.0.0-rc-3
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-rc-4
>
>
> The issue MNG-8544 made it fail in case of extension clash.
> IMO, Maven should be smarter:
> * it should apply "precedence" in case of clashes (project, user).
> * report/WARN about them to let user see, and be able to act
> * but should not fail, as this requires modifying user env that is maybe undesirable, or some other process may depend on it
--
This message was sent by Atlassian Jira
(v8.20.10#820010)