BUG: eclipse 3.7 svn vs git "projects & working sets"
Hello, Pulse Support;
BUG: eclipse 3.7 svn vs git "projects & working sets":
I am able to share SVN "projects & working sets" just fine,
and shared projects show up under "managed: shared" category;
but for GIT, the projects just keep stuck inside "not yet managed" category,
there is no error message, no nothing :-)
to view yourself: you should be able to lookup my profile by my email used for this forum;
profile name "carrot-3.7-work"; has 2 projects only; one project uses svn; another git;
any workaround for this, please?
Andrei, Pulse uses team providers to share projects, with standard psf files. To confirm this please try to export any of your egit projects. To do this, select a project that is in a git repository, open context menu and use Export -> Team -> Team Project Set, save the file and then try to import this file in a new workspace. We have tried this on our side and seem that EGit is not fully complaint with Eclipse Team provider, you can always ask to the EGit team to support this feature, in this way Pulse will also be able to support Git project share.
Thanks for using Pulse
Last edited by Pulse Support; 08-16-2011 at 09:25 AM.
thanks for looking into this;
I filed a bug with egit:
I still request you (me, as a pulse paying customer
that you bring up an error message window
when team provider does not really work with your "projects & workspaces" feature
or else people get upset with you, not git :-)
Andrei, thanks for pointing this to us, definitively we are logging an internal defect to try to detect those team providers that does not work well. The good news are that https://bugs.eclipse.org/bugs/show_bug.cgi?id=296082 is already fixed, so you will be able to get this fix as soon as Eclipse Git releases the new version.
Thanks for using Pulse
I started this thread on the Eclipse forums to bring them into the loop, but I am fairly sure this is a Pulse issue.
Using the latest nightly EGit builds, I can export a PSF file and import it manually and everything works perfectly. But if I try to share those projects using Pulse (either by sharing the projects directly or importing the PSF file into the profile) it errors out during the import.
Please look into this ASAP, as we are very anxious to get this critical feature. I will be following the progress on both sides, and am willing to help however I can with testing or whatever.
As an example, I created a PSF file containing 8 projects, all in the same Git repository. When trying to provision those projects in a new workspace, the first project simply says it failed "for an unknown reason". After that, each remaining project gives an error saying that the repository cannot be cloned because it already exists.
what do think about Mike Haney post above?
Andrei / Mike,
Very glad to hear that in the Nightly build, the project support is now working using the vanilla Import/Export Project Set. From the Pulse side, the API we use to instantiate the project is the same as the import project set model, specifically:
RepositoryProviderType.getProjectSetCapability().a ddToWorkspace(String references, serializationContext, monitor)
Where references are taken from the equivalent API during export, specifically:
RepositoryProviderType.getProjectSetCapability().a sReference(IProject projects, serializationContext, monitor)
While Pulse does have some optimizations for presentation reasons for CVS and Subversive, Pulse does not have any specific implementation specific bindings for the application or detection of projects.
For this specific issue, Andrei, I see in the original BZ that is now fixed (Bug 296082) that it was resolved on 2011-08-16. As Mike indicates, if you were using the Nightly build, it appears like this might work fine with Pulse assuming API compliance. If you use a nightly build, then this should be able to work for you.
Mike, can you provide more details as to how you added the Egit nightly build to your Pulse profile? Just getting a valid PSF would not be sufficient as you will also need the nightly Egit runtime also installed in the Pulse managed Eclipse installation.
Thanks, please let us know how it goes.