Re: spring2 release number mess

On 01/09/2012 04:44 PM, Ralph Apel wrote:
> SO then let us agree in
> 
> 2.5.6.SEC##-N.jpp6
> 
> where SEC## is part of the Version and N is our build sequence number
> for 2.5.6.SEC##
> 
> OK?

That's fine by me. Although we can't stop upstream from creating
something that doesn't work, they must obey the maven ordering rules
with respect to the `.'. So, I think for post-releases this works great.
It looks good since the RPM version matches the maven version and all
RPM dependencies also work as they should.

As far as other maven identifiers are concerned, replacing `-' by `_'
should work in RPM, but for maven, 1.0-<identifier> is < 1.0, whereas in
RPM it is > 1.0. What do to with `-' remains unclear (but, I would
probably use X_<identifier> in this case, where X can be >= 0). However,
in this scenario, we are stuck with the same problems as before. I
currently can't think of a way to solve maven pre-releases.