Hi, I am studying Maven now and I think it might be just what we need to make our builds easier and also (more important) standardizing our projects's structures.
See our scenario: We have the same trunk application but with slightly different bits and pieces which change depending on the customers we have to deploy to. For example, some clients use a customised DAO classes which relies on Stored Procedures and it also have different constraints for the table names and procedures. All the rest (about 98%) is the same for everybody. We would like to use something like: mvn install client1 and then BOOM! We have the right bits and pieces for this customers. Also is important to note we would like to have a centralised point for mantaining what is shared between the projects (which might be around 98%) and only small files (xml??) to describe the parts which change. Which would make things easier to keep it organized, I think! What is the best approach (both on SVN and Maven) to make it simple and idiots' proof ? :blush: Thanks everybody! Cheers -- View this message in context: http://www.nabble.com/Approach-for-multi-projects-based-on-same-base-code-tp19254714p19254714.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
