You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/06/01 18:44:00 UTC
[jira] [Commented] (MNG-7604) Removal of pom.* interpolation makes some older plugins defunct
[ https://issues.apache.org/jira/browse/MNG-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728458#comment-17728458 ]
ASF GitHub Bot commented on MNG-7604:
-------------------------------------
gnodet opened a new pull request, #1137:
URL: https://github.com/apache/maven/pull/1137
This reverts commit b2a21f12f8a0598dd4a286177e340bda0148e9ba.
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line and body.
- [ ] Format the pull request title like `[MNG-XXX] SUMMARY`,
where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue.
- [ ] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`.
Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message.
- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
- [ ] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
> Removal of pom.* interpolation makes some older plugins defunct
> ---------------------------------------------------------------
>
> Key: MNG-7604
> URL: https://issues.apache.org/jira/browse/MNG-7604
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 4.0.0-alpha-2
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0
>
>
> The MNG-7244 removed completely the {{pom.*}} prefix interpolation, but IMHO intent was to do it for "currently built projects". The problem is that same interpolator is used in model builder to build transitive dependency models, and with the change Maven 4 lost it's ability to resolve artifacts like wagon-http 1.0-beta-6 (used by things like surefire 2.22.2 and so on).
> The implication is that Maven4 CANNOT resolve wagon-http 1.0-beta-6 (and implicitly surefire plugin 2.22.2 is defunct it seems as it uses it). Given we have NO 3.x release of surefire (just M releases), I bet many of users out there still use 2.22.2. Also, we have no idea how many other (used as transitive dependencies) artifact exists out there doing same/similar thing that wagon POM does.
> IMHO: rollback the change from master and we need alt fix for it, as making Maven 4 unable to resolve transitive deps using pom.* placeholder introduces a huge toll.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)