One git repository for everything that is always released together and has the same version number.
If there are some sub-modules that have a different lifecycle, they should be in a separate git repository. That may force you to split the other modules you thought were always released as one into two other git repositories. Lather, rince, repeat On 21 February 2013 07:16, Eric Kolotyluk <eric.koloty...@gmail.com> wrote: > I'm a git newbie and I was wondering if there are any best practices > around using maven with git people could point me to? > > For example, if I have a project with several artifacts/modules > > net.kolotyluk.coolapp > - client.jar > - common.jar > - service.jar > > is it better to create a single repository "net.kolotyluk.coolapp" for the > project, or several repositories such as "net.kolotyluk.coolapp.client" > "net.kolotyluk.coolapp.common" and "net.kolotyluk.coolapp.**service" for > each artifact? > > Cheers, Eric > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<users-unsubscr...@maven.apache.org> > For additional commands, e-mail: users-h...@maven.apache.org > >
