[
https://issues.apache.org/jira/browse/MNG-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-7706:
---------------------------------
Description:
This expression injects type {{ArtifactRepository}} that is part of the suite
coming from Maven2 (predates Mercury, that was followed by Aether, today Maven
Resolver to be precise).
The problem with this interface is that it is not compatible (nor is possible
to adapt it) to Maven Resolver LocalRepositoryManager due lack of context.
Also, the use of this interface in Mojos causes issues like MNG-7663, as they
fully (and blidnly) reimplement Maven local repository with wired in layout.
Moreover, Mojos using this expression as shown to drag other deprecated things
as well, most typically use of maven-artifact-transfer, or
maven-dependency-tree and so on, all things that predates Maven 3.1 (are done
to "protect" from Aether package change happened between Maven 3.0 and Maven
3.1).
Today baseline for plugins is 3.2.5, so none of these "protections" are needed.
In fact, the use of this expression is very good sign of legacy and lag present
in given plugin.
was:
This expression injects type {{ArtifactRepository}} that is part of the suite
coming from Maven2 (predates Mercury, that was followed by Aether to be
precise).
The problem with this interface is that it is not compatible (nor is possible
to adapt it) to Maven Resolver LocalRepositoryManager due lack of context.
Also, the use of this interface in Mojos causes issues like MNG-7663, as they
fully (and blidnly) reimplement Maven local repository with wired in layout.
Moreover, Mojos using this expression as shown to drag other deprecated things
as well, most typically use of maven-artifact-transfer, or
maven-dependency-tree and so on, all things that predates Maven 3.1 (are done
to "protect" from Aether package change happened between Maven 3.0 and Maven
3.1).
Today baseline for plugins is 3.2.5, so none of these "protections" are needed.
In fact, the use of this expression is very good sign of legacy and lag present
in given plugin.
> Deprecate 'localRepository' mojo parameter expression
> -----------------------------------------------------
>
> Key: MNG-7706
> URL: https://issues.apache.org/jira/browse/MNG-7706
> Project: Maven
> Issue Type: Improvement
> Components: Core
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 3.9.1
>
>
> This expression injects type {{ArtifactRepository}} that is part of the suite
> coming from Maven2 (predates Mercury, that was followed by Aether, today
> Maven Resolver to be precise).
> The problem with this interface is that it is not compatible (nor is possible
> to adapt it) to Maven Resolver LocalRepositoryManager due lack of context.
> Also, the use of this interface in Mojos causes issues like MNG-7663, as they
> fully (and blidnly) reimplement Maven local repository with wired in layout.
> Moreover, Mojos using this expression as shown to drag other deprecated
> things as well, most typically use of maven-artifact-transfer, or
> maven-dependency-tree and so on, all things that predates Maven 3.1 (are done
> to "protect" from Aether package change happened between Maven 3.0 and Maven
> 3.1).
> Today baseline for plugins is 3.2.5, so none of these "protections" are
> needed. In fact, the use of this expression is very good sign of legacy and
> lag present in given plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
