Bug 395274 - Equinox returns valid bundle entries for invalid paths

 - document new osgi.strictBundleEntryPath option

1 files changed, 9 insertions, 0 deletions

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
index 85f1bd2cd..92717d6a5 100644
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
+++ b/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
@@ -756,6 +756,15 @@ will force eclipse to reinitialize these caches.</dd>
   This property is overriden by any value set in <a href="#osgisplashlocation">osgi.splashLocation</a>.</dd>
   <dt><a name="osgistartlevel"></a>osgi.startLevel</dt>
   <dd>the start level value the framework will be set to at startup.  The default value is 6.</dd>
+  <dt><a name="osgistrictbundleentrypath"></a>osgi.strictBundleEntryPath</dt>
+  <dd>
+    On some operating systems Equinox may return a bundle entry that is requested with a path that does not 
+    correspond to an actual bundle entry path. For example, on Windows file name comparison operations are 
+    case insensitive. When this property is set to true, Equinox operates more strictly by checking that the 
+    requested bundle entry path exists. The default value is false for compatibility with the previous behaviour 
+    of Equinox. This property is relevant only when the bundle is installed from a folder (not jarred) and is 
+    ignored otherwise.
+  </dd>
   <dt><a name="osgisupportmultipleHosts"></a>osgi.support.multipleHosts <span style="font-style: italic;">NEW</span></dt>
   <dd>
     if set to <b>true</b> then the framework will attempt to attach a fragment to all available host