we manage the versioning problem by using one version for all projects. for a maven release we let maven auto increment the version number. merging back into the trunk we use svn merge, but sometimes there are conflicts with poms.
--- On Thu, 6/5/08, Bryan Loofbourrow <[EMAIL PROTECTED]> wrote: > From: Bryan Loofbourrow <[EMAIL PROTECTED]> > Subject: Managing SCM branching of large, multiple-releasable-artifacts Maven > projects: ideas? > To: "Maven Users List" <[email protected]> > Date: Thursday, June 5, 2008, 3:55 PM > I'm working with Maven on a large project == many, many > Maven projects, > and multiple, separately releasable artifacts. Managing > this is pretty > reasonable, but the part I haven't figured out how to > manage efficiently > has to do with branching in my source control manager. > > > > Let's take a typical branching scenario: I want to > branch the entire > source tree, work on the branch for a while, release the > branch > artifacts under some appropriate version, then merge the > changes back to > the main trunk. In the meantime, it's likely enough > that I've done a > release from the main trunk. > > > > This is all fine, except when it comes to those version > numbers in all > of the myriad pom.xml files. That's a bit of a merge > nightmare. > > > > I can't be the only person running into this. How do > you manage this > sort of thing? > > > > Thanks, > > > > -- Bryan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
