[ https://issues.apache.org/jira/browse/MNG-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189112#comment-17189112 ]
Robert Scholte commented on MNG-6846: ------------------------------------- It depends on the kind of pom if the value of revision should be replaced or not. With MNG-6656 it will be easier to control this. > conditional overwrite > --------------------- > > Key: MNG-6846 > URL: https://issues.apache.org/jira/browse/MNG-6846 > Project: Maven > Issue Type: Bug > Components: Bootstrap & Build > Affects Versions: 3.5.0-alpha-1, 3.5.0-beta-1, 3.5.0, 3.5.2, 3.5.3, 3.5.4, > 3.6.0, 3.6.1, 3.6.2, 3.6.3 > Environment: os:windows > maven:3.6.2 > Reporter: zhaoyx > Priority: Major > Labels: beginner, newbie > Attachments: image-2020-01-10-20-51-23-490.png > > Original Estimate: 3h > Remaining Estimate: 3h > > org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator#createValueSources#lin:167 > when I use dynamic ci, I find that if the variable {{${revision}}} exists in > other projects, it will be forced to change the version. This part should be > filtered out. We cannot control the version of other projects. I tested the > sample used [mng-6846|https://github.com/zhaoyunxing92/mng-6846] -- This message was sent by Atlassian Jira (v8.3.4#803005)