Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 317364

Summary:	Workspace corruption: org.eclipse.team.core.TeamException: Could not instantiate provider org.eclipse.team.svn.core.svnnature for project
Product:	[Technology] Subversive	Reporter:	Graham Leggett <minfrin>
Component:	Core	Assignee:	Igor Burilo <igor.burilo>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	major
Priority:	P3	CC:	Szymon.Brandys
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Graham Leggett

2010-06-19 14:00:39 EDT

Build Identifier: 20100218-1602

Within an existing svn installation, all projects are suddenly listed as broken, with the exception below. All java based functionality is broken from this point: attempts to "clean" fail silently with no error, builds no longer build with no error, attempts to debug a test case fail with ClassNotFoundException, caused by the build that never happened without error.

First off, the exception is broken, as it states what Eclipse could not do, but doesn't state W H Y eclipse could not do it, and without the why, there is no fixing this bug.

Hundreds of hits come back for this in Google, and the only solution seems to be to blow away the workspace, start from scratch, and wait for the problem to happen again.

The first thing to fix is the exception, adding why the provider could not be instantiated. Once we know why, we are in a position to go to the next step, find the bug and fix it.

org.eclipse.team.core.TeamException: Could not instantiate provider org.eclipse.team.svn.core.svnnature for project apr-trunk.
at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
at org.eclipse.team.internal.core.TeamHookDispatcher.getProvider(TeamHookDispatcher.java:97)
at org.eclipse.team.internal.core.TeamHookDispatcher.getRuleFactory(TeamHookDispatcher.java:105)
at org.eclipse.core.internal.resources.Rules.factoryFor(Rules.java:92)
at org.eclipse.core.internal.resources.Rules.refreshRule(Rules.java:157)
at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1520)
at org.eclipse.core.internal.refresh.RefreshJob.runInWorkspace(RefreshJob.java:166)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)


Reproducible: Always

Steps to Reproduce:
xxx

Comment 1 Graham Leggett

2010-06-19 14:01:20 EDT

svn installation == eclipse installation

Comment 2 Szymon Brandys

2010-06-21 07:12:34 EDT

RepositoryProvider#mapNewProvider calls RepositoryProvider#newProvider that should log the root cause of the problem. I would expect to see more exceptions in the log and they may shed some light on the problem with the svn provider.

Comment 3 Graham Leggett

2010-06-21 09:21:56 EDT

Alas, the only entry in the log is the TeamException, with no nested exception, one for each project:

!ENTRY org.eclipse.team.core 4 0 2010-06-19 19:44:12.870
!MESSAGE Could not instantiate provider org.eclipse.team.svn.core.svnnature for project apr-trunk.
!STACK 1
org.eclipse.team.core.TeamException: Could not instantiate provider org.eclipse.team.svn.core.svnnature for project apr-trunk.
	at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
	at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
	at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
	at org.eclipse.team.internal.core.TeamHookDispatcher.getProvider(TeamHookDispatcher.java:97)
	at org.eclipse.team.internal.core.TeamHookDispatcher.getRuleFactory(TeamHookDispatcher.java:105)
	at org.eclipse.core.internal.resources.Rules.factoryFor(Rules.java:92)
	at org.eclipse.core.internal.resources.Rules.refreshRule(Rules.java:157)
	at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1520)
	at org.eclipse.core.internal.refresh.RefreshJob.runInWorkspace(RefreshJob.java:166)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 org.eclipse.team.core 4 0 2010-06-19 19:44:12.871
!MESSAGE Could not instantiate provider org.eclipse.team.svn.core.svnnature for project apr-trunk.

Comment 4 Alexander Gurov

2011-03-19 05:19:50 EDT

If this is the NEW Eclipse installation it probably does not have Subversive installed. Then it is understandable. If it is the Eclipse installation where Subversive WERE installed and WEREN'T uninstalled then it is definitely a strange issue. But still the Subversive plug-in is loaded by platform code and if it can't be loaded for some reason it is the Platform issue, not the Subversive's one and we can't help the situation at all.
The reason probably could be identified by looking into the Eclipse's 'features' and 'plugins' directories, checking if the Subversive plug-in is installed or not, but since the issue report is very old I doubt any suggestions will do any good now.
Also there is another point: I haven't seen nor ever heard about the issue anywhere at all. So, for now I'll be closing the report since it is not helpful and can't be solved, but if there is some additional information, please notify me and I will decide what to do with the issue next.