Type: New Feature
Affects Version/s: 1.0-alpha-5, 1.0-alpha-6
Fix Version/s: 1.0-beta-1
Number of attachments :
Require users of CBUILD lifecycles to select RPM compatible versions. Standard maven versions like.
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.