cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-43) Jenkins build process needs to allow for setting the appropriate version number within the built JARs.
Date Wed, 20 Feb 2013 16:11:17 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chip Childers closed CLOUDSTACK-43.
-----------------------------------

       Resolution: Invalid
    Fix Version/s:     (was: 4.1.0)

This is actually invalid, since we will use the mvn release process to do this outside of
jenkins.
                
> Jenkins build process needs to allow for setting the appropriate version number within
the built JARs.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-43
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-43
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: pre-4.0.0, 4.1.0
>            Reporter: Chip Childers
>            Assignee: Pradeep Soundararajan
>            Priority: Critical
>
> 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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message