Depricate release parameter requiring RPM compatible versioning
---------------------------------------------------------------
Key: CBUILDS-38
URL: http://jira.codehaus.org/browse/CBUILDS-38
Project: Mojo C Builds
Issue Type: New Feature
Affects Versions: 1.0-alpha-6, 1.0-alpha-5
Reporter: Lee Thompson
Fix For: 1.0-beta-1
Require users of CBUILD lifecycles to select RPM compatible versions. Standard
maven versions like.
1.0-alpha-1
1.0-beta-2
1.0-alpha-1-SNAPSHOT
do not behave the same with RPMs. Also, RPMs require a build number, which is
currently coded as "release". Devise a versioning scheme and error out if the
version is not compatible. Allow overloads so that users who understand the
problems can overcome the error.
For instance, in maven, 1.0-alpha-1 is before 1.0. In RPM it is after. With
this change, the default behavior will be to fail if "-alpha-" is encountered
in the version. Also, this change will require the version to end in a dash
character followed by a number which will represent the RPM build (aka release)
number. If it is not present, this will fail with no overload.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
