That's exactly how we manage the version #s for branches. We use the
convention that the leading number comes from the source of the branch
(usually the trunk), then we add a meaningful identifier for the branch, and
finally a branch version that can be incremented by the release process -
6.0.0-m
who said version numbers have to be numbers!
6.0.0-mybranch-SNAPSHOT
6.0.0-yourbranch-SNAPSHOT,
etc
On 16 April 2010 13:09, Nicola Musatti wrote:
> Stephen Connolly wrote:
>
>> different branches should have different version numbers
>>
> This would be reasonable if I only issued maintenance r
If you branch, you must change the version in the pom
Jeff
Envoyé de mon VT100 Phone
Le 16 avr. 2010 à 12:12, Nicola Musatti
a écrit :
Hallo,
I have different branches of the same project that are being
developed in parallel, to cater for customer customizations. Is
there a standard w
different branches should have different version numbers
On 16 April 2010 11:12, Nicola Musatti wrote:
> Hallo,
> I have different branches of the same project that are being developed in
> parallel, to cater for customer customizations. Is there a standard way to
> identify the resulting artifa
Hallo,
I have different branches of the same project that are being developed
in parallel, to cater for customer customizations. Is there a standard
way to identify the resulting artifacts? At first I thought of giving
each a different classifier, but I'm under the impression that this is
not
