[
https://issues.apache.org/jira/browse/MDEPLOY-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965666#comment-17965666
]
Olivier Lamy commented on MDEPLOY-94:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#147|https://github.com/apache/maven-deploy-plugin/issues/147].
> Variables in the version element in pom.xml need to be expanded before
> deployment
> ---------------------------------------------------------------------------------
>
> Key: MDEPLOY-94
> URL: https://issues.apache.org/jira/browse/MDEPLOY-94
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Reporter: Brian Jackson
> Assignee: John Dennis Casey
> Priority: Major
>
> We use an external tool to manage our releases (instead of
> maven-release-plugin). The version in our pom.xml is declared as:
> <version>${build.number}</version>
> The actual version number is passed in during a release deployment on the
> command line "mvn deploy -Dbuild.number=1.2.3"
> The pom.xml is deployed literally without the variable replaced with the
> actual value. This causes problems, in particular multi-module releases are
> impossible since the parent pom can't be resolved properly as well as this
> issue with Nexus https://issues.sonatype.org/browse/NEXUS-1552
> I started digging into the code and see deployment is deferred to the
> DefaultArtifactDeployer
> http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.html
> Can I somehow install a custom ArtifactTransformation that expands these
> variables before deployment? How would I install it in my builds? Would I
> build it as a Plexus component and add it as a plugin dependency of
> maven-deploy-plugin? If someone could give me a little guidance I'd be happy
> to implement it, test it and submit a patch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
