[MNG-7912] Support ${project.*} in file profile activation
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Jimisola Laursen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER281352)** opened **[MNG-7912](https://issues.apache.org/jira/browse/MNG-7912?redirect=false)** and commented
The official docs clearly states that:
"The tags \ and \ 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.
---
**Issue Links:**
- [MNG-7895](https://issues.apache.org/jira/browse/MNG-7895) Support ${project.basedir} in file profile activation
Contributor guide
Assessment
This issue has not been assessed yet.