On 21/06/12 6:50 PM, Fabrizio Giudici wrote:
On Thu, 21 Jun 2012 03:24:01 +0200, Mark Derricutt <m...@talios.com>
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.
It's a combination - a big part that is definitely git/mercurial based
is that unlike subversion - git tags/branches are repository wide rather
than at a directory level. If you have n projects in a repository and
you want to work on different branches of each project, then you need to
make SEPARATE checkouts of the entire repository.
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To post to this group, send email to javaposse@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
