You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arnoud Glimmerveen (Jira)" <ji...@apache.org> on 2020/05/22 17:28:00 UTC
[jira] [Commented] (MNG-6912) File based profile activation results
in absolute paths in OriginalModel
[ https://issues.apache.org/jira/browse/MNG-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114269#comment-17114269 ]
Arnoud Glimmerveen commented on MNG-6912:
-----------------------------------------
I noticed there was already an issue for this problem.
> File based profile activation results in absolute paths in OriginalModel
> ------------------------------------------------------------------------
>
> Key: MNG-6912
> URL: https://issues.apache.org/jira/browse/MNG-6912
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.6.3
> Reporter: Arnoud Glimmerveen
> Priority: Major
>
> If a project has one or more profiles activated using file(s), the _OriginalModel_ that a maven plugin can obtain from the MavenProject, holds the absolute path to these files, rather than the raw value from the pom.xml file.
> This is caused by the DefaultModelBuilder using the 'rawModel' to determine the active profiles, which has the side-effect of interpolating the files to absolute paths.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)