Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0-alpha-5, 1.0-alpha-6
-
Fix Version/s: 1.0-beta-1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
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.
Good documents on RPM versioning
http://fedoraproject.org/wiki/Tools/RPM/VersionComparison
http://fedoraproject.org/wiki/Packaging/JPackagePolicy
Maven versioning
http://docs.codehaus.org/display/MAVEN/Versioning