[MNG-2971] Variables are not replaced into installed pom file
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 40m
- Merged PRs (30d)
- 275
Description
**[Laurent Dauvilaire](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ldauvilaire)** opened **[MNG-2971](https://issues.apache.org/jira/browse/MNG-2971?redirect=false)** and commented
Variables are not replaced into installed pom file.
Here is a sample pom file
```xml
4.0.0
com.xxx.root
root
pom
${prop.version}
My Project
...
3.0.20
```
The installed pom is into ${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
---
**Attachments:**
- [pom.xml](https://issues.apache.org/jira/secure/attachment/12713350/pom.xml) (_452 bytes_)
**Issue Links:**
- [MNG-4369](https://issues.apache.org/jira/browse/MNG-4369) Maven does not expand expressions while installing artifacts locally
(_**"duplicates"**_)
- [MNG-4223](https://issues.apache.org/jira/browse/MNG-4223) Resolve expressions in POM artifact coordinates
- [MNG-4161](https://issues.apache.org/jira/browse/MNG-4161) possibility to omit version in dependency of same project (and fill in on install/deploy)
- [MNG-3057](https://issues.apache.org/jira/browse/MNG-3057) properties not expanded in generated POMs when building A/B/C nested projects
- [MNG-624](https://issues.apache.org/jira/browse/MNG-624) automatic parent versioning
- [MNG-3267](https://issues.apache.org/jira/browse/MNG-3267) replacing variables in version, groupId or artifactId when POM is installed/deployed
- [MINSTALL-50](https://issues.apache.org/jira/browse/MINSTALL-50) provide property filtering on .pom files placed in local repo
(_**"depends upon"**_)
43 votes, 51 watchers
Contributor guide
Assessment
This issue has not been assessed yet.