Skip to main content
aboutsummaryrefslogtreecommitdiffstats
path: root/egit.psf
AgeCommit message (Collapse)AuthorFilesLines
2012-11-09Update egit.psf team project setRobin Stocker1-14/+34
Change-Id: I8ea59a4915dee73305285989ff0c6979baa76fe6
2011-08-16Team project set supportRobin Stocker1-0/+19
This is based on the previous work by Mykola Nikishov in change I800dd9f23953ad903f20289c442707e2dde08f75 ("Import a project set file"). This change includes export support, unit tests, and can handle the situation where different branches of the same repository should be imported. A project reference string in the project set file looks like this: 1.0,git://egit.eclipse.org/egit.git,master,org.eclipse.egit Based on an array of these reference strings, GitProjectSetCapability does the following when importing: - Clone a repository with CloneOperation for each combination of repository URL and branch name. - Import a project from each directory that is specified in the last part of the string ("." if the repository itself is the .project). - Add the repository to the Repositories View. - Connect the projects using ConnectProviderOperation. Due to Bug 244313, import and export of project set files requires the org.eclipse.core.runtime.compatibility plug-in. The dependency is in a separate optional feature, as proposed on the old change. It's required for Eclipse < 3.7. CQ: 5438 Bug: 296082 Change-Id: I1500cc376961117b39b8760e6de675a4885e5f72 Also-by: Mykola Nikishov <mn@mn.com.ua> Signed-off-by: Robin Stocker <robin@nibor.org> Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>

    Back to the top