[
https://jira.codehaus.org/browse/MDEPLOY-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed MDEPLOY-60.
-----------------------------------
Resolution: Won't Fix
The uniqueVersion that is used by the deploy plugin when deploying -SNAPSHOTs
is only determined at the time of deployment. There is currently no way to
obtain that information ahead of deployment.
The only way I could see of achieving this would be to have a separate goal
that allocates this value and can be attached to the validate phase of the
lifecycle... if that goal were run then it would override deploy's default
behaviour... but it would run the risk of breaking too many things.
The correct solution is to just use the release plugin to make a release of the
project. Putting a lot of effort in to making -SNAPSHOTs durable is not what
-SNAPSHOTs are about
> Make the build number available at compile time
> -----------------------------------------------
>
> Key: MDEPLOY-60
> URL: https://jira.codehaus.org/browse/MDEPLOY-60
> Project: Maven 2.x Deploy Plugin
> Issue Type: Improvement
> Affects Versions: 2.3
> Reporter: Antony Stubbs
>
> Make the build number which goes into the final filename of a deployed
> snapshot, available at compile time, so that it can be filtered into a
> properties file and used in the application. There are a lot of requests for
> this on the forum, including people trying to implement their own
> work-arounds [1]
> There could also be an option to specify a custom build number - e.g. the
> subversion revision number which is retrieved via the build number plug-in
> [2].
> [1]
> http://www.nabble.com/Auto-incrementing-a-build-identifier-tf2319084s177.html#a12026347
> [2]
> http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/introduction.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
