Package Details: eclipse-subclipse 4.3.3-1

Git Clone URL: https://aur.archlinux.org/eclipse-subclipse.git (read-only, click to copy)
Package Base: eclipse-subclipse
Description: Subversion integration for the Eclipse platform
Upstream URL: https://github.com/subclipse/subclipse
Keywords: eclipse java subversion svn
Licenses: EPL
Provides: subclipse
Submitter: xyproto
Maintainer: fungible
Last Packager: fungible
Votes: 48
Popularity: 0.000000
First Submitted: 2011-12-14 17:01 (UTC)
Last Updated: 2021-12-21 22:55 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

rdg commented on 2012-07-25 05:27 (UTC)

Ok, I went through uninstalling all my packages and it seems that eclipse-emf was the culprit. Luckily I don't need it so I am up and working now. Thanks for the help everyone.

Bevan commented on 2012-07-24 22:58 (UTC)

Nice find. I'm glad to hear that you could solve the issue :) Hopefully this helps rdg, too. I don't think eclipse-cdt is the culprit. I also have it installed and I don't experience any problems.

darose commented on 2012-07-24 22:41 (UTC)

Ah HAH! Problem solved! One of the eclipse plugin packages I had installed must have been interfering with subclipse. I had the following installed: eclipse 4.2-1 eclipse-android 18.0.0-2 eclipse-cdt 8.1.0-2 eclipse-dltk-core 3.0.1-1 eclipse-emf 2.7.2-2 eclipse-findbugs 2.0.0-1 eclipse-gef 3.7.2-2 eclipse-linuxtools 0.10-1 eclipse-shelled 2.0.1-1 eclipse-subclipse 1.8.14-1 eclipse-wtp-wst 3.3.2-8 Once I uninstalled everything except for eclipse and eclipse-subclipse, problem went away. When (if?) I have a moment I'll try to add these back in one at a time and see which one(s) caused the conflict.

darose commented on 2012-07-24 22:32 (UTC)

Well, here's a clue: I checked the eclipse error log, and it generates several of these exceptions on startup: org.eclipse.team.core.TeamException: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project Cabsense. 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:93) at org.eclipse.core.internal.resources.Rules.deleteRule(Rules.java:80) at org.eclipse.core.internal.resources.Resource.delete(Resource.java:782) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.cleanOutputFolders(BatchImageBuilder.java:114) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:46) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Anyone have any idea what could be causing this?

darose commented on 2012-07-24 16:55 (UTC)

I can confirm what rdg reported. I created a brand new workspace, and added my project to that. But I can't access Team -> Share project (SVN), can't show any of the SVN views, etc. Any ideas why subclipse doesn't work with the newer version of Eclipse?

rdg commented on 2012-07-20 04:40 (UTC)

I have tried with a clean environment and still have the same problem.

darose commented on 2012-07-16 17:42 (UTC)

I haven't, no. Will try that when I get a moment.

Bevan commented on 2012-07-16 16:52 (UTC)

Hmmm, interesting. I just checked again and I have an SVN view and can import via SVN. Also using eclipse 4.2 and subclipse 1.8.13. Have you already tried to set up a clean environment? (move ~/.eclipse somewhere else and use a new workspace)

darose commented on 2012-07-16 14:26 (UTC)

Yes, I see the exact same problem as rdg.

rdg commented on 2012-07-14 20:06 (UTC)

I am having this problem as well. Eclipse install details reports that the software is installed, however it doesn't work -- there is no SVN view available or SVN import option. Not sure if this is related but it is basically the same thing that happens if you try to install as a regular user via the internal eclipse package manager.

« First ‹ Previous 1 2 3 4 Next › Last »