On Fri, Nov 5, 2010 at 2:10 PM, Phillip Hellewell <[email protected]> wrote:
> On Fri, Nov 5, 2010 at 3:00 PM, Phillip Hellewell <[email protected]> > wrote: > > Thanks Jeorg. I will look into having a dependencyManagement section > > in parent pom as you and Jon suggested. That should at least help > > alleviate things a bit... > > Sorry to reply to myself, but I have a really big question about all > this. How do you handle dozens of artifacts, all of which may have > several versions going concurrently, like on different branches. Is > there a single parent pom that contains all dependency versions for > all artifacts on all branches? That seems like it could get very > complicated. Or would have a bunch of different parent poms > (actually, that seems even more complicated.) So do you have parallel streams of development all shooting for a common release date? Or do you have parallel releases with seperate dates -- usually one occurring after the next in time. If parallel development, just put each stream in its own branch, and set the affected version to a snapshot. Hand that off to a developer and wait. When the developer hands the completed code back, merge the branch into the trunk/main/master branch and increment or change the version of the artifacts they updated. Repeat until everyone is done, then hand it over to QA. The key here is to let your SCM keep track of the various versions of pom files and dependencies via braching, and then merge it all back together when the development task is done.
