When you create new branch to do a bug fix for something like webservices, but the fix resides at a low level, maybe in a utils package.
Do you branch both the area you're changing AND the consumer of the change together (see my example below), or do you branch them individually? Either way, how do you exclude modules then from that top level pom.xml? Can you do that in a profile? -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 5:42 PM To: Maven Users List Subject: Re: Source control structure for Maven projects That's how we're doing it as well, more or less. Except we're using SVN and it appears you're using something else. What specifically are you looking for in the way of best practices? Wayne On 6/1/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > Hello list! Is there any best practices docs I could be pointed to for > this? We'd like to do something like: > > //depot/srvcs/project/project-1/module-1/pom.xml > //depot/srvcs/project/project-1/module-2/pom.xml > //depot/srvcs/project/project-1/module-3/pom.xml > //depot/srvcs/project/project-1/pom.xml > > What is everyone else doing? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
