Community
Participate
Working Groups
3.6 RC1 Steps: * check out "org.eclipse.debug.examples.core" and ""org.eclipse.debug.examples.ui" into your workspace * create a feature with the two plug-ins * export the feature to a directory with metadata * close the projects in the workspace * launch an Eclipse application with "support software installation" checked on the configuration tab * install the example feature into the target * restart The feature appears as installed, but the plug-ins are not present, nor is the launch configration type (PDA) when opening the LCD.
Needs investigation
The profile has the installed bundles, but the bundles are not known to OSGi (opening the OSGi console and running ss does not list the bundles). The bundles.info is not overwritten when the installation occurs, but it is rewritten on restart. cc'ing John and Pascal. Maybe they can shed some light on what is happening.
I expect that the bug in PDE here is that we are writing bundles.info on restart. We have code to avoid overwriting the profile on restart. However, the fact that simple configurator is not updating bundles.info after the install suggests there is something else wrong here. This isn't a priority for 3.6 as the purpose of the feature was to provide a modifiable profile when self hosting, which works fine. It's just unfortunate that the UI for the feature says "Allow installation of software into the running target" which doesn't work.
I'm suspecting that the profile does not have proper values for paths like install area and the like which consequently causes the bundles.info to be written out in the wrong place. A good way to track that would be to put a breakpoint in SimpleConfiguratorManipulatorImpl#save() (in simpleconfigurator.manipulator bundle) and see where / if the file is written out.
(In reply to comment #4) > I'm suspecting that the profile does not have proper values for paths like > install area and the like which consequently causes the bundles.info to be > written out in the wrong place. A good way to track that would be to put a > breakpoint in SimpleConfiguratorManipulatorImpl#save() (in > simpleconfigurator.manipulator bundle) and see where / if the file is written > out. I put a breakpoint in the save() and saveConfigurations() method, however, none of them were ever hit.
I looked at that a bit and the first thing I noticed is that none of the configuration units (.e.g tooling.osgi.default) appear in the profile. This means that at install time, the jars will only be downloaded but they will never be installed in the OSGi runtime. Matt tried some hacked where he forced the tooling.osgi.default CU to be added, however the provisioning operation failed part way through the installation of the bundle (InstallBundleAction) in a NPE which made me suspect that the profile was probably not properly setup (missing some of the properties like install path, bundle pool path, etc.). However we did not had enough time to continue the investigation any further.
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.
