You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jimisola Laursen (Jira)" <ji...@apache.org> on 2023/10/16 12:55:00 UTC
[jira] [Created] (MNG-7912) Support ${project.*} in file profile activation
Jimisola Laursen created MNG-7912:
-------------------------------------
Summary: Support ${project.*} in file profile activation
Key: MNG-7912
URL: https://issues.apache.org/jira/browse/MNG-7912
Project: Maven
Issue Type: Improvement
Reporter: Jimisola Laursen
The official docs clearly states that:
"The tags <exists> and <missing> can be interpolated. Supported variables are system properties like ${user.home} and environment variables like ${env.HOME}. Please note that properties and values defined in the POM itself are not available for interpolation here, e.g. the above example activator cannot use ${project.build.directory} but needs to hard-code the path target."
We have a use-case where another maven run will create an artifact which we want to attach at a later run if a particular file exists. However, this file is generated as
${project.build.directory}/${project.build.finalName}-classifier.zip
Presently, ${project.*} can't be used in file profile activation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)