On Thu, 21 Jun 2012 03:24:01 +0200, Mark Derricutt <[email protected]> wrote:
One main issue to be aware of with git ( and I assume mercurial ) is that you HAVE to release from the root of your repository, which pushes you to a single module/artifact per repository.
I assume this is not a SCM problem, rather a release-plugin constraints: I define this saying that a master pom defines the "atomicity" of a release (my rules are a repo root for each master pom). This doesn't mean you need to put only a single module instead. This means that you need to release all of the underlying modules at the same time. Which often makes sense by design reasons (e.g. the modules are cohese, etc...). So it all boils down to breaking the project into sub-project partitions, each one with a master pom and a repo root, in an appropriate way.
-- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." [email protected] http://tidalwave.it - http://fabriziogiudici.it -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
