[ https://issues.apache.org/jira/browse/MNG-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Heinz Marbaise updated MNG-6253: ------------------------------------- Fix Version/s: waiting-for-feedback > Replace CI friendly variables in pom.xml when installing/deploying > ------------------------------------------------------------------ > > Key: MNG-6253 > URL: https://issues.apache.org/jira/browse/MNG-6253 > Project: Maven > Issue Type: Improvement > Affects Versions: 3.5.0 > Reporter: Christoph Amshoff > Fix For: waiting-for-feedback > > > When using variables in pom.xml to get CI friendly version > (https://maven.apache.org/maven-ci-friendly.html), these will not be replaced > in installed or deployed pom files, which makes them unusable for other > builds. > Karl Heinz Marbaise suggested to use the flatten-maven-plugin to do the > property replacement > (http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/), > and this was also suggested as a workaround in other tickets (MDEPLOY-223 > got closed with "Not A Problem" solution). > That indeed works, but flatten-maven-plugin has to be manually configured in > the base POM, and additionally it changes the pom files in many other areas > which you would not want. > I honestly think that property replacement for the three allowed properties > ({{$\{revision\}}}, {{$\{sha1\}}}, {{$\{changelist\}}}) should be done by > Maven internally without having the user configure other plugins. The feature > is just not correctly working without, so closing such issues with "Not A > Problem" is too little. -- This message was sent by Atlassian JIRA (v6.4.14#64029)