Eclipse Community Forums: EGit / JGit » Recommended Git Repository layout for multi-project workspace?

Help

Home

Home » Eclipse Projects » EGit / JGit » Recommended Git Repository layout for multi-project workspace?

Show: Today's Messages :: Show Polls :: Message Navigator

Thu, 10 May 2012 08:48

Guido Scalise

Messages: 16
Registered: April 2012

Junior Member

I'm starting working in a multi-plugin, multi-product (client/server) RCP+Jetty project, with the intention of reusing some of the plugins/OSGi bundles in client and server, and I have some doubts regarding the ideal repository layout.

I mean... I know that when checking out a branch of a project, all the projects in the repository are switched to the branch as well, so having all of the plugins in a single repository might not be a good idea at all.

The second solution would be creating a repository for each plugin, which I assume would be a nightmare as well.

The third solution (and maybe the most adequate) would be to have a group of plugins (features maybe?) per repository, but I'd like to know your experience before deciding something based only on my maybe-not-that-common sense.

So... What would be, for you, the ideal/recommended repository=>plugin layout? Could sub modules be my silver bullet?

Cheers,
Guido

[Updated on: Thu, 10 May 2012 08:56]

Report message to a moderator

Thu, 10 May 2012 14:05

Matthew Webber

Messages: 198
Registered: December 2010

Senior Member

We have multiple repositories, with each repository containing multiple Eclipse projects (features, plugins, etc). We try and group projects so that "related" ones (for some definition of related) are in the same repository - that often corresponds to a feature project and its plugins - your third solution.

We don't use submodules (I think EGit only got support for them recently).

When deciding what set of feature/plugins/etc belong together in a repository, think about what gets released together. For us, making a release means making a (specially named) branch, so all the components that will always get released together go in the same repo.

We use Buckminster so that developers don't need to know which repository holds a given component.

Report message to a moderator

Tue, 22 May 2012 14:48

Ondrej Medek

Messages: 23
Registered: July 2009

Junior Member

Just adding: Maybe you can use Maven (Gradle) instead of Buckminster. Have one project/repository with Maven configuration, which ties plugins together.

[Updated on: Tue, 22 May 2012 14:48]

Report message to a moderator

Previous Topic:	How to bring back a project from local repository to workspace
Next Topic:	Can't commit and sometimes not add, but works on the CLI

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 27 04:24:46 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter