You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/12/08 20:00:00 UTC
[jira] [Commented] (MNG-6870) A maven project can't fetch its
parent when its repository is configured with an interpolated variable
[ https://issues.apache.org/jira/browse/MNG-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246119#comment-17246119 ]
Michael Osipov commented on MNG-6870:
-------------------------------------
[~rfscholte], here is your dup: MNG-6457.
> A maven project can't fetch its parent when its repository is configured with an interpolated variable
> ------------------------------------------------------------------------------------------------------
>
> Key: MNG-6870
> URL: https://issues.apache.org/jira/browse/MNG-6870
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Inheritance and Interpolation
> Affects Versions: 3.6.3
> Reporter: Arnaud Rivero
> Priority: Major
>
> Maven seems to be unable to fetch its parent pom.xml on a remote repository when it uses an interpolated variable in its repositories configuration.
> However, if no parent is declared in the same project pom.xml and the parent is declared as a dependency instead, then it is downloaded.
> If we have both the parent configured and declared as a dependency, the same problem occurs : Maven can't download the parent from the remote repository
> Lastly, if we replace the variable by its value, there are no problem downloading the parent pom.xml
> The problem occurs whether the variable is a property defined in the pom.xml or is an environment variable
>
> It seems maven can only interpolate a variable value in a pom.xml after the parent has been resolved
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)