Community
Participate
Working Groups
Now that CVS is no longer distributed by the platform, EGIT should not complain about its absence. The errorlog below shows an unnecessary log from a project that does not have a cvsnature but does have a CVS folder. Could not instantiate provider org.eclipse.team.cvs.core.cvsnature for project lpg.generator. org.eclipse.team.core.TeamException: Could not instantiate provider org.eclipse.team.cvs.core.cvsnature for project lpg.generator. at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:168) at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:236) at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:513) at org.eclipse.egit.core.Activator$CheckProjectsToShare.visitConnect(Activator.java:656) at org.eclipse.egit.core.Activator$CheckProjectsToShare.run(Activator.java:629) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Ed, please remove lpg.generator from workspace and add it again. In your old Eclipse you had CVS installed, and project mapped to it. Now in your new Eclipse, there is no CVS and so the "team" code has issues to share this project with Git, because it still believes it should use CVS. I tend to close this as user error.
In any case not an EGit problem. EGit's just asking the platform's team support whether a project is shared with some team provider. Team support finds this stale info that the project was shared with CVS, cannot find CVS, and then team support complains. Nothing EGit can do about it.
OK. Moving to pfatform team. Looks like there is missing migration support to accommodate stale workspace metadata.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
REOPENing and not stale until a member of the platform team has at least considered the problem since migration from EGIT.
