Branching and merging poms

[John Coleman <jo...@eurobase-international.com>]

Hi,

We develop different code bases for out clients, and this means having
various branches of our generic codebase running in parallel. We
envisage that some branches will have the poms changed, maybe to
introduce new dependencies, or dependencies on a variety of versions.

What concerns us is that during merges between branch and trunk, client
customised poms will get muddled up. Therefore we want to seperate the
poms in a way that allows each project to choose the pom based on its
client name property, probaly gathered from a profile.

Has anyone a nice solution to this? We are using multi module projects,
and I was thinking we can use almost empty poms in the project and
inherit through a relative path to the client specific poms. Or should
we just have a number of different pom file names? In which case how do
we standardise the build?

Regards,
John

Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. 

Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited.  If you receive this transmission in error, please notify us immediately, and then delete this E-mail. 

Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments.

Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org