Community
Participate
Working Groups
Build Identifier: 3.7 egit does not support standard psf format: http://www.poweredbypulse.com/forums/showthread.php?1501-BUG-eclipse-3.7-svn-vs-git-quot-projects-amp-working-sets-quot Reproducible: Always Steps to Reproduce: try to exprot psf for both svn and git and re-import them into a different workspace; svn works; git does not; http://www.poweredbypulse.com/forums/showthread.php?1501-BUG-eclipse-3.7-svn-vs-git-quot-projects-amp-working-sets-quot
We just implemented this targetting the 1.1 release (see bug 296082) *** This bug has been marked as a duplicate of bug 296082 ***
I don't think this is really a duplicate - if you look at the linked thread on the Pulse forum, you'll see that they are pointing to EGit as the problem for not supporting the team provider spec correctly. Using the latest nightly build, if I export a PSF with EGit projects and then import it into a new workspace, it works as expected. However, if I try to share those projects using Pulse (which uses the team project set capabilities to do this), it fails when trying to clone the repository in the new workspace. Unfortunately, the error message is pretty useless. When trying to add a PSF with 8 projects (all from the same git repo), the first project it just says it failed "for an unknown reason". After that are 7 error messages from (I presume) JGit saying that the repository already exists in that location and it's aborting the cloning operation.
Then file a bug against Pulse, it's work like expected for us.
