Re: Review Request: CLOUDSTACK-43 : Jenkins build process needs to allow for setting the appropriate version number within the built JARs.

[Hugo Trippaers <ht...@schubergphilis.com>]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7083/#review12065
-----------------------------------------------------------


Heya,

There is no need to make this change in the pom.xml files. Maven includes a mechanism to get this done automagically, but we will need to prepare for this.
In maven land a release is a onetime event where a release manager decides to push a button and a release happens. To support this maven has the release:prepare goal to help the release manager with this.

This goal will create a tag in the version management system, temporary update the pom to show a release version  (i.e. ditch the -SNAPSHOT extension) and push all created artifacts to the maven repository. This is a nice pointer to the related documentation: http://maven.apache.org/guides/mini/guide-releasing.html

Cheers,

Hugo

- Hugo Trippaers


On Sept. 25, 2012, 12:46 p.m., Pradeep Soundararajan wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/7083/
> -----------------------------------------------------------
> 
> (Updated Sept. 25, 2012, 12:46 p.m.)
> 
> 
> Review request for cloudstack, Chip Childers and edison su.
> 
> 
> Description
> -------
> 
> The Jenkins binary build processes are producing JAR files that contain version numbers like 4.0.0-SNAPSHOT. We need a way to set a parameter within the build to set the version from SNAPSHOT to RC1 or even drop the pre-release identifier entirely (so that we can generate an actual release). 
> 
> >> Removed the occurrences of SNAPSHOT
> 
> 
> Diffs
> -----
> 
>   agent/pom.xml a559580 
>   api/pom.xml db14775 
>   awsapi/pom.xml a583384 
>   client/pom.xml 50b85e9 
>   cloud.spec 908a411 
>   console-proxy/pom.xml 8bfb753 
>   core/pom.xml 510cb04 
>   debian/cloud-deps.install 74aade1 
>   deps/XenServerJava/pom.xml 1337514 
>   deps/pom.xml 1e20083 
>   patches/pom.xml d62fc86 
>   plugins/deployment-planners/user-concentrated-pod/pom.xml ca2fae1 
>   plugins/deployment-planners/user-dispersing/pom.xml 6e1ffc6 
>   plugins/file-systems/netapp/pom.xml f10e5a4 
>   plugins/host-allocators/random/pom.xml ad66c0e 
>   plugins/hypervisors/kvm/pom.xml 4863085 
>   plugins/hypervisors/ovm/pom.xml a8b23d0 
>   plugins/hypervisors/vmware/pom.xml 435ae38 
>   plugins/hypervisors/xen/pom.xml bf38e47 
>   plugins/network-elements/elastic-loadbalancer/pom.xml c1ab2c5 
>   plugins/network-elements/f5/pom.xml 0cba48c 
>   plugins/network-elements/juniper-srx/pom.xml 38a2b55 
>   plugins/network-elements/midokura-midonet/pom.xml 7f2e2d3 
>   plugins/network-elements/netscaler/pom.xml 377e6e0 
>   plugins/network-elements/nicira-nvp/pom.xml 37c3a3a 
>   plugins/network-elements/ovs/pom.xml 02d455c 
>   plugins/pom.xml 206d4a1 
>   plugins/storage-allocators/random/pom.xml 6cb60cd 
>   plugins/user-authenticators/ldap/pom.xml 7facc3f 
>   plugins/user-authenticators/md5/pom.xml 1dac92d 
>   plugins/user-authenticators/plain-text/pom.xml a4280a3 
>   pom.xml e3e535a 
>   server/pom.xml f7178d8 
>   test/pom.xml f70a89f 
>   usage/pom.xml 92e5e72 
>   utils/pom.xml e8d7827 
>   vmware-base/pom.xml 1dabe83 
>   wscript_build 4264822 
> 
> Diff: https://reviews.apache.org/r/7083/diff/
> 
> 
> Testing
> -------
> 
> Able to execute mvn install successfully after the changes...
> 
> 
> Thanks,
> 
> Pradeep Soundararajan
> 
>