incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "edison su" <edison...@citrix.com>
Subject Re: Review Request: CLOUDSTACK-43 : Jenkins build process needs to allow for setting the appropriate version number within the built JARs.
Date Thu, 13 Sep 2012 18:10:11 GMT

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


Are you sure the the build system will generate jars with 4.0.0-snapshot? We use ant not maven
to JARs, so the version number in pom.xml doesn't impact the JARs at all.

- edison su


On Sept. 13, 2012, 4:28 p.m., Pradeep Soundararajan wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/7083/
> -----------------------------------------------------------
> 
> (Updated Sept. 13, 2012, 4:28 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 
>   console-proxy/pom.xml 8bfb753 
>   core/pom.xml 510cb04 
>   deps/XenServerJava/pom.xml 1337514 
>   deps/pom.xml be30c9a 
>   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 2d1a001 
>   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 972d645 
>   server/pom.xml f7178d8 
>   test/pom.xml f70a89f 
>   usage/pom.xml 92e5e72 
>   utils/pom.xml e8d7827 
>   vmware-base/pom.xml 1dabe83 
>   wscript f1c9b62 
> 
> Diff: https://reviews.apache.org/r/7083/diff/
> 
> 
> Testing
> -------
> 
> Able to execute mvn install successfully after the changes...
> 
> 
> Thanks,
> 
> Pradeep Soundararajan
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message