Hallo,
I need advice on how to handle naming/versioning for artifacts built
from separate branches of the same project, which evolve in parallel.
Our product has a main, "standard" development line, but customers
usually ask for customizations that make it necessary to spin off
separate variants.When this happens each variant starts to follow its
own time-line, with its own release schedule.
From an SCM point of view - we use subversion - this translates to the
standard product being developed on trunk while customer variants live
in separate branches. Ideally the project's directory structure should
be the same across variants, but resulting artifacts should be
identifiable, e.g.:
project-x.y.z for the standard product
project-customer-m.n.o for a customer variants
To further complicate things our product is actually made of several
different Maven sub-projects and a customer variant is usually a
combination of standard and customized sub-projects. We use an
aggregator project to build the whole product. Different variants of
this aggregator project combine the correct mix of standard and
customized sub-projects.
Suggestions are very welcome!
Cheers,
Nicola Musatti
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
