Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EGit/User Guide/Project Set File"

(Export a project set file)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
An original enhancement request [https://bugs.eclipse.org/bugs/296082  Bug 296082 -  Provide support for Project Set Files] has [https://bugs.eclipse.org/bugs/attachment.cgi?id=153089 a fake PSF] for EGit and JGit projects.
+
An original enhancement request {{bug|296082}} has [https://bugs.eclipse.org/bugs/attachment.cgi?id=153261 a sample PSF] for EGit and JGit projects. [http://egit.eclipse.org/r/118 Simple implementation] is available for review.
 +
 
 +
If you'd like to try it:
 +
 
 +
{{warning|As it's 'work-in-progress' I would highly recommend you not to use any workspace with a valuable data!}}
 +
 
 +
:*Download [https://bugs.eclipse.org/bugs/attachment.cgi?id=154856 an archived update site] from Bugzilla;
 +
:*Add it to the list of available update sites (Help - Install new software... - Add... - Archive... )
 +
:*Install 'Eclipse Git Feature (Incubation)'
 +
:*Download [https://bugs.eclipse.org/bugs/attachment.cgi?id=153261 a sample PSF] for EGit and JGit projects  
 +
:*Import PSF (File - Import... - Team Project Set)
  
 
== Import a project set file  ==
 
== Import a project set file  ==
  
=== Corner cases ===
+
=== Corner cases ===
  
==== Same branch VS individual branches ====
+
==== 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
+
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
 
:*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.
+
Creating two (identical?) local repositories will be required to support individual branches.  
  
 
== 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.
+
 
 +
:*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.

Latest revision as of 11:53, 20 December 2009

An original enhancement request bug 296082 has a sample PSF for EGit and JGit projects. Simple implementation is available for review.

If you'd like to try it:

Warning2.png
As it's 'work-in-progress' I would highly recommend you not to use any workspace with a valuable data!


  • Download an archived update site from Bugzilla;
  • Add it to the list of available update sites (Help - Install new software... - Add... - Archive... )
  • Install 'Eclipse Git Feature (Incubation)'
  • Download a sample PSF for EGit and JGit projects
  • Import PSF (File - Import... - Team Project Set)

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:

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.

Back to the top