[ https://issues.apache.org/jira/browse/MRELEASE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16359091#comment-16359091 ]
Robert Thornton edited comment on MRELEASE-935 at 2/9/18 11:27 PM: ------------------------------------------------------------------- I would also like the release plugin to support this feature. For example, maven does support the ${revision} expression in the version tag in which case the <revision> property is expected not to have any expressions inside it. See: https://maven.apache.org/maven-ci-friendly.html However, the ${revision} expression is lost when the release plugin sets the development version. I've attached a patch that resolves this issue. [^support_for_revision_in_version.patch] was (Author: rptmaestro): I would also like the release plugin to support this feature. For example, maven does support the ${revision} expression in the version tag in which case the <revision> property is expected not to have any expressions inside it. However, the ${revision} expression is lost when the release plugin sets the development version. I've attached a patch that resolves this issue. [^support_for_revision_in_version.patch] > Support for expression in 'version' tag > --------------------------------------- > > Key: MRELEASE-935 > URL: https://issues.apache.org/jira/browse/MRELEASE-935 > Project: Maven Release Plugin > Issue Type: New Feature > Affects Versions: 2.5.3 > Reporter: Andrea Scarpino > Priority: Critical > Attachments: support_for_revision_in_version.patch > > > The release plugin doesn't support a version value that points to a property > which define the version. > Everytime I use the plugin, the version in the current POM loose the > expression. Maybe it could work using the property to which it points? > {noformat} > $ grep '<version>' pom.xml > <version>${parent.project.version}</version> > $ grep '<parent.project.version>' pom.xml > <parent.project.version>0.0.1-SNAPSHOT</parent.project.version> > {noformat} > Could you please implement this or point me to the files that handle this? -- This message was sent by Atlassian JIRA (v7.6.3#76005)