Bug 568726: Document osgi.dataAreaRequiresExplicitInit

Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
Change-Id: Ic2f551c3410e75e7ca09c466ca18858221481bcd

bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html

@@ -546,6 +546,13 @@ <h2>System properties</h2>
      that was set when the framework launched (default value).</li>
     </ul>
   </dd>
+  <dt><a name="osgidataAreaRequiresExplicitInit"></a>osgi.dataAreaRequiresExplicitInit</dt>
+  <dd>if &quot;true&quot;, don't allow clients to initialize instance location if the instance
+    area is not explicitly defined yet. This prevents a plug-in that starts early from accessing
+    the instance area before it has been configured by the osgi.instance.area setting.
+    It is recommended to set osgi.dataAreaRequiresExplicitInit=true.
+    See <a href="#osgiinstancearea">osgi.instance.area</a>.
+  </dd>
   <dt><a name="osgidebug"></a>osgi.debug {-debug}</dt>
   <dd>if set to a non-null value, the platform is put in debug mode. If the value
     is a string it is interpreted as the location of the
@@ -690,7 +697,8 @@ <h2>System properties</h2>
   <dd>the instance data location for this session. Plug-ins use this location
     to store their data. For example, the Resources plug-in uses this as the
     default location for projects (aka the workspace). See the section on <a href="#locations">locations</a> for
-    more details.</dd>
+    more details. Set <a href="#osgidataAreaRequiresExplicitInit">osgi.dataAreaRequiresExplicitInit</a> to ensure
+    that data area is explicitly initialized before plug-ins can use it.</dd>
   <dt><a name="osgiinstanceareadefault" id="osgiinstanceareadefault"></a>osgi.instance.area.default</dt>
   <dd>the default instance data location for this session. Plug-ins use this
     location to store their data. For example, the Resources plug-in uses this