Hi,
We have the fairly typical scenario where we want to build different "flavours" of an application for our clients. Typically each client requires a different set of properties files, for example, but there might be further changes to the resources or classes. How should we leverage Maven2 to achieve the best compromise between repetition and reuse? At present we have Ant scripts with a lot of repetition to do each customer build by packaging the common and unique client files together. My initial thought is to build a core JAR and have separate projects that use this as a dependency, but it seems to make more sense to use the subproject approach so we can at least inherit some of the common POM properties like the company details and developer team. Perhaps the core code could also go in a common project, but be used simply to graft source code from rather than create an artefact? John Coleman, MSTA Senior Developer Consultant Eurobase Banking Solutions Bury House, 31 Bury Street, London EC3A 5AG, U.K. Office: +44 (0)1245 496 706, Fax: +44 (0)20 7626 6203 Mobile: +44 (0)7734 506586 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.
