Community
Participate
Working Groups
Build Identifier: 20100617-1415 I extracted official eclipse-java-helios-linux-gtk.tar.gz tarball as root:root, and started Eclipse as a regular user. When I try to install subclipse using Eclipse MarketPlace apparently goes by just fine, but SVN isn't available after Eclipse is restarted (it doesn't even appear on Preferences > Team). Eclipse logs shows this: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project xxx. StackTrace: (attached) Session data: eclipse.buildId=I20100608-0911 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.java.product Additional info: I unchecked "CollabNet Merge Client" option during Subclipse installation. Reproducible: Always Steps to Reproduce: 1. unpack Helios official tarball 2. chmod -R root:root 3. execute Eclipse as a regular user 4. install Subclipse using Eclipse MarketPlace (uncheck "CollabNet Merge Client")
Created attachment 172561 [details] Stacktrace logged on error log
I just confirmed: changing ownership to the user that runs eclipse (or giving write access to the Eclipse installation dir) "fixes" this problem. Not sure if it's exactly the same thing as bug #287246, but it does seems related (and also to bug #315853 which I reported against RC4). With Linux usage as the preferred platform for development on the rise and SVN accountig for almost 60% of SCM usage (according to Eclipse Community Survey 2010), installing Subclipse as a regular user on a root-owned Eclipse installation on Linux is a trivial test that should be done before a release. Sorry for the rant, I know a lot of effort is put into making Eclipse the best IDE around, and I am really grateful for it. It's just that it's really frustrating, I was hoping Helios would finally fix these problems and allow shared installs on Linux.
Simon could you please see what is going on using regular p2 UI? I wonder if this is not a problem with the market place client.
Hi Pascal, I don't think it's a problem with the MarketPlace client, because I first tried it "manually" (directlty from Subclipse update URL), and the result was the same (sorry I forgot to mention that). I then retried through the MarketPlace client just to make sure I hadn't done anything wrong -- and to try it out, of course ;-) (it's a nice feature BTW)
From the p2 side we seem to think the installation was successful. Andre do you have any idea on how to determine what subclipse things is wrong. Is it possible some component is making a bad assumption on a path to a library or configuration file??
(In reply to comment #5) > From the p2 side we seem to think the installation was successful. Andre do you > have any idea on how to determine what subclipse things is wrong. Is it > possible some component is making a bad assumption on a path to a library or > configuration file?? Hi Simon, I am not sure, maybe there is. One thing that I noticed is that installation through MarketPlace client only brings JavaHL support, which is required by Subclipse but not installed by default on Linux AFAIK (if you install directly from Subclipse update site you have the option of choosing SVNKit support, which is what I use). But, I don't think this is the problem, because the symptom of having Subclipse installed but no JavaHL is that Subclipse appears as installed (it appears on Preferences, files on the Package Explorer view show the SCM specific decorations etc.), but an (annoying ;-)) error dialog keeps popping up saying that something is wrong; once you install SVNKit support and configures Subclipse to use it, it works as expected. (I just went through this very same situation here on my Helios installation) What I see when Eclipse is installed as root:root is that Subclipse simply "disappears silently": installation ends without noticeable errors (aside from the error log) but there's no trace of Subclipse anywhere. Can you reproduce this ("missing Subclipse") with the setup I described? BTW: a colleague here just complained that he had reinstalled Helios from scratch 2 times on his Linux box trying to make Subclipse work :-( I confirmed he had installed it as non-readable to his UID.
Simon, the stack trace shows that the TeamException happens on org.eclipse.team.core.RepositoryProvider, and is caused by a call to org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations. So, it might not be a p2 problem after all, I might have misled you by filing this as a p2 bug. Please apologize if that's the case.
FWIW, as commented in bug 317896, I wasn't able to reproduce a problem with installing subclipse into a shared install on Windows Vista.
Hi. Is this still being investigated? Could I help with any additional info?
Created attachment 173534 [details] diff result the diff file to compare the share configuration and user configuration
I can reproduced this issue on linux. And I think it should have similar root cause with 317896. My steps are, 1. download helios java development tool(eclipse-java-helios-linux-gtk.tar.gz) 2. use root user to unzip it, for example sudo tar xzvf eclipse-java-helios-linux-gtk.tar.gz /opt/ 3. launch it as normal user, then install git from eclipse marketplace 4. restart the eclipse, however git can't work due to the git plug-ins are not loaded. Even though the p2 profile has recored the git as installed. The configuration, p2 data and plugins could be found my home ~/.eclipse/org.eclipse.platform_3.5.0_1473617060. I checked the bundles.info for default eclipse package and my personal configuration, I found the some bundles are recorded in default bundles.info that don't exist actually! They are: ch.qos.logback.classic ch.qos.logback.core ch.qos.logback.slf4j javax.mail.glassfish org.eclipse.net4j.jms.api org.slf4j.api See attached diff result for more detail. Hence the user plug-ins array doesn't contain the share plug-ins, equinox.simpleconfigurator bundle installs the bundles from share plug-ins! That's why the newly installed plug-ins not work.
*** This bug has been marked as a duplicate of bug 322929 ***
