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

Bug 367210

Summary: [reconciler] Trouble finding dropins or links content when running via UNC and using config.ini for custom configuration area
Product: [Eclipse Project] Equinox Reporter: Helmut J. Haigermoser <helmut.haigermoser>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.7.1   
Target Milestone: ---   
Hardware: All   
OS: Windows 7   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=366547
Whiteboard: stalebug

Description Helmut J. Haigermoser CLA 2011-12-20 11:14:52 EST 
Build Identifier: 

Our product puts all configuration data in the users home. This is done via config.ini slot using the "osgi.configuration.area" key.

Doing so works nicely in most scenarios but we do see issues using UNC paths. Looks like the dropped-in content is still found by p2 as it's displayed in the Installed Software view, but the content is missing from the osgi runtime...




Reproducible: Always

Steps to Reproduce:
1. Share local directory C:\dir as \\<local host name>\dir
2. Extract fresh Eclipse into C:\dir
3. Drop RXTX into C:\dir\eclipse\dropins
4. Modify config.ini to include 
osgi.configuration.area=@user.home/.workbench-3.3.2.20111028-1147_@install.hash/configuration

5. Start up Eclipse via \\<local host name>\dir\eclipse\eclipse.exe
6. Help->About Eclipse SDK -> Installation Details
Comment 1 Helmut J. Haigermoser CLA 2011-12-20 11:16:13 EST 
CQ:WIND00224870

*setting Version to 3.7.1*
*relating to another bug we found*

Check that other bugzilla, https://bugs.eclipse.org/bugs/show_bug.cgi?id=366547, for a screenshot of RXTX not showing up in any but the first "Installation Details" screen...
Comment 2 Eclipse Genie CLA 2019-09-06 17:55:54 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.