[
https://issues.apache.org/jira/browse/MNG-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768559#comment-17768559
]
ASF GitHub Bot commented on MNG-7895:
-------------------------------------
gnodet commented on code in PR #1262:
URL: https://github.com/apache/maven/pull/1262#discussion_r1335478151
##########
api/maven-api-model/src/main/mdo/maven.mdo:
##########
@@ -3007,7 +3007,7 @@
is the location of a file that needs to exist, and if it doesn't, the
profile will be
activated. On the other hand, {@code exists} will test for the
existence of the file and if it is
there, the profile will be activated.<br>
- Variable interpolation for these file specifications is limited to
{@code ${basedir}},
+ Variable interpolation for these file specifications is limited to
{@code ${project.basedir}},
Review Comment:
Would it make sense to also support `session.rootDirectory` ?
> Support ${project.basedir} in file profile activation
> ------------------------------------------------------
>
> Key: MNG-7895
> URL: https://issues.apache.org/jira/browse/MNG-7895
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
> Reporter: Slawomir Jaranowski
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 4.0.0-alpha-8, 3.9.5
>
>
> Profile activation by file exists or missing should allow to use
> ${project.basedir}
> Currently only {{${basedir}}} can be used ... but short properties are
> deprecated
> It can confusing users.
> Documentation to fix:
> https://maven.apache.org/pom.html#activation
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
