| Submodules? [message #525369] |
Tue, 06 April 2010 07:43  |
Eclipse User |
|
|
|
What's the current status of support for submodules in jgit/egit? If they're not yet supported is there any (even very hand-wavy) estimate for when support might land?
Alternatively, if there's no support currently, what are peoples recommendations for structuring a collection of sources which includes multiple Eclipse projects but where a subset of these are "external" (ie. there's a set of projects which would logically fit into a single git repository, but a couple of additional ones which would ideally grouped together with the first set via a superproject). However it's done I'd like to be able to support atomic commits across all the projects.
Any pointers would be very welcome.
|
|
|
|
|
| Re: Submodules? [message #540385 is a reply to message #540150] |
Tue, 15 June 2010 19:23  |
| Eclipse User |
|
|
|
Lester Caine wrote:
> No comments on this other than some vague request to explain?
(Must be an old tread, not in the news server anymore)
>
> I have been running eclipse/phpeclipse for many years and have been more
> than happy, but one of my projects as 'bitten the bullet' and decided
> 'git' is the way forward from CVS. The source CVS project has 157 CVS
> modules which are combined to build a project. Only modules that are
> complete and functional are included in production builds. So from CVS you
> can download a group of modules such as 'core'. GIT was a real pain to
> port this very basic structure into, but it has now been done, with some
> command line scripts to handle each module, and the result is 157 git
> repos, with superprojects to replace the CVS packages ...
Deciding how to divide your project into different repositories is a hard
decision. Whichever way you divide will probably have a smaller impact
than you may think, though 157 repo seems about 30 time too many (without
actually looking). I have to idea about your product structure, so I cannot
say it doesn't make sense. Some of the methods I see sometimes is having
completely separate repos development. The Git way is branches that gets
to the main branch using merge, cherry-pick or whatever make best sense.
In Git you can have branches in separate repos is size of the alpha repos
is a worry.
As for submodule support in JGit, I have no idea when that will appear. I
imagine someday. I've never used them myself, and I'm not sure I ever will,
partially because I don't think they solve the problem of linking
repositories well. The links are too strong and only work with other Git
repos.
What I would use is something more like the Android's repo tool, the team
project set, custome shell scripts or some other CM tool that can bring
together a lot of sources, whether they reside in git, cvs or some other
scm. Currently I to this manually and howegrown CM scripts for build
automation.
> Come on egit to download .... I only sees the basic 'master' branch, and
> fails even to download from that.
"fails" is not much of a description of the problem. Can't help with that,
but it relates to submodule, then that is the problem. We should probably
detect that and tell the user about the problem in a nice way. I'm not
sure we do.
> So does this question need bouncing over to jgit?
Yes, JGit needs submodule for EGit to support them. It's the same forum
though.
-- robin
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04737 seconds
Home