Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EGit/User Guide/Project Set File"
< EGit | User Guide
(→Import a project set file) |
(→Export a project set file) |
||
| Line 13: | Line 13: | ||
== Export a project set file == | == Export a project set file == | ||
| + | :*Local working copy of the project shared with CVS, SVN (as any other centralized VCS?) has a reference to a single remote repository. But it's not the case for a Git (and for any other distributed VCS?). A several remotes may be configured for a local Git repository and user should provide which one should be referenced from a PSF. | ||
Revision as of 06:12, 26 November 2009
An original enhancement request Bug 296082 - Provide support for Project Set Files has a fake PSF for EGit and JGit projects.
Contents
Import a project set file
Corner cases
Same branch VS individual branches
It's OK if all referenced projects share the same branch. Does it make sense to support individual branches (per project) like this:
- Project 'org.eclipse.jgit' from the 'master' in 'git://egit.eclipse.org/egit/parallelip-jgit.git' repository
- Project 'org.eclipse.jgit.pgm' from the 'cq-diff' in 'git://egit.eclipse.org/egit/parallelip-jgit.git' repository
Creating two (identical?) local repositories will be required to support individual branches.
Export a project set file
- Local working copy of the project shared with CVS, SVN (as any other centralized VCS?) has a reference to a single remote repository. But it's not the case for a Git (and for any other distributed VCS?). A several remotes may be configured for a local Git repository and user should provide which one should be referenced from a PSF.