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

Bug 330150

Summary:	Modifying dropins directory to read-only access does not load plug-ins
Product:	[Eclipse Project] Equinox	Reporter:	hollisc
Component:	p2	Assignee:	DJ Houghton <dj.houghton>
Status:	RESOLVED NOT_ECLIPSE	QA Contact:
Severity:	major
Priority:	P3	CC:	daniel_megert, pwebster, tjwatson
Version:	3.6.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description hollisc

2010-11-12 16:48:50 EST

Build Identifier: Eclipse 3.6.1 

Reproduced on Windows 2008, Windows 7 and Linux OS as well.

Reproducible: Always

Steps to Reproduce:
1. Add plugins to the dropin directory
2. Make the dropin directory read-only
3. Start eclipse as admin

Result: Plugins added are not loaded
Expected: Plugins are loaded

If you launch Eclipse using admin before making the directory as read-only, you will not see the problem.

Comment 1 DJ Houghton

2010-11-12 16:52:22 EST

Just to be clear, this is with 3.6.1 in a shared install scenario.

- install Eclipse as root
- add bundles to root/eclipse/plugins/ folder
- switch to user
- start Eclipse

Note: did not start Eclipse as root before starting as user.
Note: need to also test bundle in root/dropins/ location as well.

Comment 2 DJ Houghton

2010-11-16 11:45:22 EST

I have tried to reproduce this on XP but couldn't. What I did:
- install Eclipse 3.6.1
- add bundle A to plugins
- add bundle B to dropins
- mark the install as read-only
- start Eclipse
- note in the OSGi console that both A and B are installed

I will try on Linux.

Comment 3 DJ Houghton

2010-11-16 12:02:59 EST

I get the same results on Linux, everything works as expected. Hollis are there more detailed steps to reproduce this problem? Are you able to reproduce it with a basic Eclipse or only when there is a product install involved?

Comment 4 DJ Houghton

2010-11-17 14:24:51 EST

It appears the problem is not reproducible right now with plain Eclipse, only with the Eclipse-based product. Further investigation is required.

Comment 5 DJ Houghton

2010-12-20 12:02:53 EST

Turns out this was a problem with the adopting product and not Eclipse itself.