I had seen that in the release notes, about support for sparse checkouts. However I still think that approach/model will lead to issues if/when someone checkout the whole repo not knowing should should use sparse mode.
I'll have to try it out sometime and see just how well it works. -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On Tue, Jul 5, 2011 at 10:46 PM, Olivier Lamy <[email protected]> wrote: > Note : a hack has been added in last release 2.2 for this use case. > > HTH, > -- > Olivier Lamy > http://twitter.com/olamy | http://www.linkedin.com/in/olamy > > [1] http://jira.codehaus.org/browse/MRELEASE-457 > > 2011/7/5 Mark Derricutt <[email protected]>: > > Regardless of your choice between git or mercurial ( I vote git btw ) be > > aware that due to git/mercurials tagging model, and how > maven-release-plugin > > works, maven works better with an artifact per repository model. > > > > So instead of having 3-4 artifacts in a single repo you'll need to split > > them up ( unless you want a single version number for all things ). > > > > After we switched from subversion to git I wrote up a short post on what > I > > did: > > > > > http://theoryinpractise.tumblr.com/post/1350252794/repository-migration-from-subversion-to-git > > > > Hope it helps. > > > > PS: git git git git git git git ;-) > > > > -- > > "Great artists are extremely selfish and arrogant things" — Steven > Wilson, > > Porcupine Tree > > > > > > On Mon, Jul 4, 2011 at 11:27 PM, Peter Horlock < > [email protected] > >> wrote: > > > >> Hi! > >> > >> We are planning to move from SVN to either GIT or Mercurial. > >> What would you recommend using? > >> Which has the better Maven / Eclipse / Sonar Support? > >> > >> Thanks, > >> > >> Peter > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
