[news.eclipse.technology.equinox] Re: Eclipse osgi.configuration on Vist

[michael.sacarny@xxxxxxxxxx ( MSacarny)]

Simon,
I've fixed most, but not all, the problems.

My eclipse.ini file was:
-startup
plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-vmargs
-Dosgi.instance.area.default=@xxxxxxxxx/VisualDSP Andromeda
-Dosgi.configuration.cascaded=false

My config.ini was:
#This configuration file was written by: 
org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxFwConfigFileParser
#Fri Jun 26 14:46:45 EDT 2009
org.eclipse.update.reconcile=false
eclipse.p2.profile=VISUALDSPProfile
osgi.framework=file\:plugins/org.eclipse.osgi_3.5.0.v20090520.jar
osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.1.0.v20090601.jar@1\:start,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.100.v20090520-1905.jar@1\:start
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info
eclipse.product=com.analog.visualdsp.product
osgi.splashPath=platform\:/base/plugins/com.analog.visualdsp
osgi.framework.extensions=reference\:file\:org.eclipse.equinox.transforms.hook_1.0.100.v200906261443.jar
osgi.bundles.defaultStartLevel=4
eclipse.p2.data.area=@xxxxxxxxxx/../p2/
eclipse.application=org.eclipse.ui.ide.workbench

The biggest problem was:
-Dosgi.configuration.cascaded=false

We had this set 'false' in order to get our transform plugins working 
during development, as it is set that way in sample code for 
org.eclipse.equinox.transforms.xslt.plugin. However, the transforms now 
seem to work with this entry removed from the ini file, so I plan to take 
it out. When I do this, each user gets his own config space automatically 
under @user.home/.eclipse/<unique product hash>, and multi-user scenarios 
seem to work very well. Users can upgrade/uninstall independently of each 
other. I see no sign of file virtualization. Even the 'Dropins' folder 
works, although is shared.

The only problem I see at this point is the default "Available Software 
Site" I build into the product. It's not visible for any user. It 
originates in p2.inf colocated with the product file at build time. We 
build with SDK 3.5 but the build style is as in 3.4.1, that is, using 
p2.generate.metadata. The site info is in the product in:
eclipse\p2\org.eclipse.equinox.p2.engine\profileRegistry\VISUALDSPProfile.profile\<profile 
files>
and also in:
eclipse\p2\org.eclipse.equinox.p2.engine\profileRegistry\VISUALDSPProfile.profile\.data\.settings\*.prefs 


but doesn't seem to get picked up in the Vista configuration. Works fine 
in XP.

I'm going to try and follow Niefer's comments in 
http://www.eclipse.org/newsportal/article.php?id=1833&group=eclipse.platform.pde#1833
about including p2.inf in our bundles. Maybe colocating with the product 
file is insufficient.

Thanks!
Mike

Any help would be appreciated.