Home » Eclipse Projects » Eclipse Platform » Per-user plugin/dependencies broken between 3.4.1->3.4.2 (and beyond) 
| Per-user plugin/dependencies broken between 3.4.1->3.4.2 (and beyond) [message #335822] | 
Fri, 01 May 2009 13:22   | 
 
Eclipse User  | 
 | 
 | 
   | 
 
Hi, 
 
When using eclipse 3.4.1, if I extracted eclipse into some central place  
on my machine and then et the permissions on it so that, when invoked by a  
normal user (e.g. my own personal user account) it could NOT write to that  
directory, installing plugins would magically go into the .eclipse folder  
for that particular build and everything worked. 
 
Starting with 3.4.2, this behaviour seems to have changed because  
installing plugins and restarting eclipse results in the error box being  
displayed, and the log shows it seems to think it is missing all the key  
jar files. 
 
So, two my two questions are as follows: 
1) what changed in the handling of dependencies between 3.4.1 and 3.4.2  
that caused such huge behavioural differences? 
 
2) If the way I had it working before was a fluke and has just become  
deprecated, why was it not explicitly mentioned somewhere and a new  
solution for per-user plugins documented? I have searched and searched and  
every other solution refers to parts of the software update GUI that no  
longer exist in 3.4+(like managed configuration.....can't find it any more  
on OS X), or dropins folder which i cannot seem to get update sites to  
install to. 
 
Would really appreciate advice because 3.4.2 contains some nice fixes to a  
few issues, but not being able to get plugins working is becoming a real  
show stopper for me. 
 
Cheers, Alex J Burke.
 |  
 |  
  |  
| Re: Per-user plugin/dependencies broken between 3.4.1->3.4.2 (and beyond) [message #335840 is a reply to message #335822] | 
Mon, 04 May 2009 09:54    | 
 
Eclipse User  | 
 | 
 | 
   | 
 
Alex J Burke wrote: 
> Hi, 
>  
> When using eclipse 3.4.1, if I extracted eclipse into some central place  
> on my machine and then et the permissions on it so that, when invoked by  
> a normal user (e.g. my own personal user account) it could NOT write to  
> that directory, installing plugins would magically go into the .eclipse  
> folder for that particular build and everything worked. 
>  
> Starting with 3.4.2, this behaviour seems to have changed because  
> installing plugins and restarting eclipse results in the error box being  
> displayed, and the log shows it seems to think it is missing all the key  
> jar files. 
>  
> So, two my two questions are as follows: 
> 1) what changed in the handling of dependencies between 3.4.1 and 3.4.2  
> that caused such huge behavioural differences? 
>  
> 2) If the way I had it working before was a fluke and has just become  
> deprecated, why was it not explicitly mentioned somewhere and a new  
> solution for per-user plugins documented? I have searched and searched  
> and every other solution refers to parts of the software update GUI that  
> no longer exist in 3.4+(like managed configuration.....can't find it any  
> more on OS X), or dropins folder which i cannot seem to get update sites  
> to install to. 
>  
> Would really appreciate advice because 3.4.2 contains some nice fixes to  
> a few issues, but not being able to get plugins working is becoming a  
> real show stopper for me. 
>  
> Cheers, Alex J Burke. 
>  
 
Routing to equinox,  p2 is responsible for finding plugins in 3.4.x 
 
Have you run the steps for multi-user installs [1] when you created the  
3.4.1 install?  How did you update to 3.4.2, using  
http://download.eclipse.org/releases/ganymede ? 
 
Later, 
PW 
 
[1]  
 http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.platform.doc.isv/reference/misc/multi_user_installs.html 
 
 
 
--  
Paul Webster 
http://wiki.eclipse.org/Platform_Command_Framework 
http://wiki.eclipse.org/Command_Core_Expressions 
http://wiki.eclipse.org/Menu_Contributions 
http://wiki.eclipse.org/Menus_Extension_Mapping 
 http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.platform.doc.isv/guide/workbench.htm
 |  
 |  
  |  
| Re: Per-user plugin/dependencies broken between 3.4.1->3.4.2 (and beyond) [message #335856 is a reply to message #335840] | 
Tue, 05 May 2009 12:19   | 
 
Eclipse User  | 
 | 
 | 
   | 
 
Hi, 
 
Sorry it's taken a while to reply....I thought I had posted one and then  
noticed that it seems to have been eaten. Here is attempt number two. 
 
To try to isolate the issue I decided to do a fresh install of 3.4.2 based  
on the multi-user instructions you presented - although that is the  
process I had largely been using. Specifically, it is the installation  
area I made read only. 
 
I extracted 3.4.2, made sure it is read-only for normal users (including  
myself), and then ran ./eclipse -initialise to set the configuration as  
the user owning the platform. So far so good, and eclipse came up. 
 
Now, I went into the software updates, added the site for AnyEdit and  
installed version 2.2.0. When presented with the option I opted to restart  
eclipse, and on next load I was presented with "An error has occurred." 
 
The following is an excerpt from the log that was generated: 
 
!SESSION 2009-05-05 17:08:49.350  
----------------------------------------------- 
eclipse.buildId=M20090211-1700 
java.version=1.5.0_16 
java.vendor=Apple Inc. 
BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US 
Framework arguments:  -keyring /Users/alex/.eclipse_keyring -showlocation 
Command-line arguments:  -os macosx -ws carbon -arch x86 -keyring  
/Users/alex/.eclipse_keyring -consoleLog -showlocation 
 
!ENTRY org.eclipse.osgi 4 0 2009-05-05 17:08:50.106 
!MESSAGE Startup error 
!STACK 1 
java.lang.IllegalArgumentException: Bundle  
" reference:file:plugins/org.eclipse.core.runtime_3.4.0.v20080 512.jar " has  
been uninstalled 
	at  
 org.eclipse.osgi.framework.internal.core.StartLevelManager.g etBundleStartLevel(StartLevelManager.java:371) 
	at  
 org.eclipse.core.runtime.adaptor.EclipseStarter.ensureBundle sActive(EclipseStarter.java:446) 
	at  
 org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Ecli pseStarter.java:335) 
	at  
 org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175) 
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
	at  
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39) 
	at  
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25) 
	at java.lang.reflect.Method.invoke(Method.java:585) 
	at  org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549) 
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) 
	at org.eclipse.equinox.launcher.Main.run(Main.java:1236) 
 
!ENTRY org.eclipse.osgi 2 0 2009-05-05 17:08:50.163 
!MESSAGE One or more bundles are not resolved because the following root  
constraints are not resolved: 
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-05-05 17:08:50.163 
!MESSAGE Bundle  
 reference:file:plugins/org.eclipse.ltk.core.refactoring_3.4. 2.r342_v20081028-0800.jar  
was not resolved. 
!SUBENTRY 2 org.eclipse.ltk.core.refactoring 2 0 2009-05-05 17:08:50.163 
!MESSAGE Missing required bundle org.eclipse.core.runtime_[3.3.0,4.0.0). 
 
It seems to go on for almost ever core jar until it mentions that jar file  
version constraints were not met for AnyEdit. 
 
One curious thing, the extensions folder for 3.4.1 was named: 
~/.eclipse/org.eclipse.platform_3.4.0_1916030313 
but for 3.4.2: 
~/.eclipse/org.eclipse.platform_3.4.0_1916030312 
 
Does it think it somehow went back a version? Could this be related? 
 
Btw, if there is anything else I can provide please just let me know, this  
is a really irritating one! As I said this is happening on everything  
3.4.2 and over. 
 
Cheers, Alex J Burke.
 |  
 |  
  |   
Goto Forum:
 
 Current Time: Tue Nov 04 00:26:39 EST 2025 
 Powered by  FUDForum. Page generated in 0.03634 seconds  
 |