ESOE Project on git? - ESOE Development

Message from discussion ESOE Project on git?

Luke Daley

More options Jun 18, 2:58 pm

From: Luke Daley <lda...@gmail.com>

Date: Thu, 18 Jun 2009 14:58:46 +1000

Local: Thurs, Jun 18 2009 2:58 pm

Subject: Re: [esoe-dev] Re: ESOE Project on git?

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

On 18/06/2009, at 10:41 AM, Bradley Beddoes wrote:

> My experience with other large projects and Git has been the single
> repository approach with top level directories for each sub component.
> I've used a couple that have gone the other way. Overall there are
> positives and negatives to both.

I prefer smaller repositories.

This does cause issues with branching/tagging etc, but it may be a
good opportunity to investigate whether all of the modules need to be
bound to the same version number and release cycle.

If a monolithic repository can be avoided, I think that should be the
path.

> What I find does really get painful with the single repository
> approach is folks storing binaries (jars etc) that cause pulls to take
> a long time especially from international sources. ESOE to date has
> done a very good job of not storing any binary in SCM and has made
> good use of Ivy et al for dependency resolution.

This is painful even with multiple. But at least with multiple you can
isolate the pain.

For example, the Grails plugin does have binaries in svn.
Unfortunately this is really unavoidable. If it was it's own repo it
wouldn't be infecting the whole project.

> GitHub is a lot more useful as a web-app with single repository in my
> experience.

Can't you emulate a lot of this by a “meta” project that pulls
everything in as a module?

> I guess as long as the dependency resolution approach continues and is
> strongly enforced I'd be leaning towards a single approach but it
> doesn't concern me either way.

What's that? You want to use Maven? :P

Reply to author Forward