[ 
http://jira.codehaus.org/browse/MDEPLOY-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165112#action_165112
 ] 

John Casey commented on MDEPLOY-94:
-----------------------------------

I've added a link to MNG-3057 as this is basically the same issue. I'll take a 
look at how we can revisit these issues for 2.1.0 as soon as I'm done with 
another issue that I'm testing at the moment. You might have some luck doing 
what Brian proposed on the maven dev list, and prepend the path to your jar 
into the m2.conf file in $(maven.home)/bin.

If you have a patch that will interpolate all versions in the POM, can you post 
it?

> Variables in the version element in pom.xml need to be expanded before 
> deployment
> ---------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-94
>                 URL: http://jira.codehaus.org/browse/MDEPLOY-94
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Bug
>            Reporter: Brian Jackson
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to