OK, I have added my two cents at http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide?focusedCommentId=230398624#comment-230398624
Someone need to replace the Latin in front matter. If you want I could do that, and promote my comment into the article. Cheers, Eric On Thu, Feb 21, 2013 at 9:20 AM, Stadelmann Josef < josef.stadelm...@axa-winterthur.ch> wrote: > Unfortunately the link below does not show anything to read in English ... > Josef > > -----Ursprüngliche Nachricht----- > Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > Gesendet: Donnerstag, 21. Februar 2013 15:54 > An: Maven Users List > Betreff: Re: Git Repositories > > You would imaging somewhere like: > http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide > > But documentation of best practices is something we are weak on... > > We are great at telling people what isn't best practice... not so great at > documenting that stuff ;-) > > A wise user would add a child page to that wiki page, and perhaps remove > the placeholder text! (Given that the linked page is the *user* contributed > wiki) > > > On 21 February 2013 14:47, Eric Kolotyluk <eric.koloty...@gmail.com> > wrote: > > > OK, I think I've got it. > > > > The answer depends more on what artifacts will always have the same > > version number, than how many artifacts there are. > > > > In a nutshell, one repository for the entire multi-module project is > > best, where all the artifacts keep their versions in sync with the > parent pom. > > > > But, if you have to support artifacts with versions out of sync, then > > the out of sync versions need their own repositories. More work to > > manage, but sometimes necessary. > > > > Thanks for the clarification. Where would I find these kinds of best > > practices written down? > > > > Cheers, Eric > > > > > > On 2013-02-21 1:25 AM, Stephen Connolly wrote: > > > >> 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.**apac**he.org<http://apache.org> > >>> <users-unsubscribe@**maven.apache.org<users-unsubscribe@maven.apache > >>> .org> > >>> > > >>> > >>> For additional commands, e-mail: users-h...@maven.apache.org > >>> > >>> > >>> > > > > ------------------------------**------------------------------**------ > > --- To unsubscribe, e-mail: > > users-unsubscribe@maven.**apache.org<users-unsubscr...@maven.apache.or > > g> For additional commands, e-mail: users-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
