Community
Participate
Working Groups
As we work towards removing the old Update Manager and its APIs from Eclipse (bug 311590) we should investigate the removal of the platform.xml file. Currently the eclipse.touchpoint modifies this file when we install new features. I believe this is because the update configurator reads the file and registers a BundleGroupProvider to provide feature details to the About dialog. Bug 236709 covers p2 registering a BundleGroupProvider. Is there anything else that we use the platform.xml file for?
John and I were talking about this bug and also bug 236709. Just wanted to capture some of the conversation here. Specially we were wondering if we could get to the point where we don't need to install the feature JARs at all. What information do they include that isn't already in the metadata? So far all we could come up with is an optional pointer to the feature's primary plug-in (which contains the branding information). If this isn't specified then we look for a plug-in with the same ID as the feature itself. This led to an interesting conversation about interoperability with Update Manager. The UM bundles (other than update.configurator) are not shipped in the 4.2 stream. But in 3.8 (I believe) users can still enable the Classic Update capability to use UM to install features. There is also the case of install handlers. In p2 we provide touchpoint actions which are intended to replace install handlers but if we try and do an install and we run across an install handler, then we defer to the UM to do the install for us. If it is a matter of just doing the install, then we might be ok. But if there is any validation done beforehand, then it would fail. The UM would only know about the features listed in the platform.xml file and since that file is empty, it would say your configuration is invalid. We need to verify this behaviour and see if validation is done previous to the install. Also things like the Manage Configuration window just plain wouldn't work. One approach that is ok to take is you can use UM or p2 but they won't understand each other. This is fine in all cases except when p2 uses UM to install features with install handlers and if validation is performed as part of the operation.
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.
This bug was marked as stalebug a while ago. Marking as wontfix. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
