We have a project that I am preparing to convert from Ant to Maven2, but it is rather complex and I am not sure the best way to proceed.
There are two difficulties: 1. We must support different versions, such as standalone and client-server via RMI. These require small changes in the build process, such as which property files are included, running rmic, and so on. 2. We must support customizations for each customer. This includes differences in property files and possibly code changes on CVS branches. Also, different customers use different version (as above) - sometimes just one, sometimes many. Ultimately, I need to create a packaging with the customized code (if any), and all the different versions. Presumably, this will require that the customized versions be deployed under a different name. My thought was to use profiles for (1), and append some string to the final name (such as "-rmi"). Then on each CVS branch I could modify the artifactId (and possibly groupId) for each customer. I don't know whether I should have some sort of parent-child relationship, or whether I should just use dependencies. Any suggestions? Has anyone dealt with a similar situation? -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
