Community
Participate
Working Groups
Created attachment 168885 [details] target platform profile I've installed XULRunner feature by extracting it into a dropins/ folder. The feature includes four platform-dependent fragments. I've added those fragments into my feature.xml file: <plugin id="org.mozilla.xulrunner.win32.win32.x86" os="win32" ws="win32" arch="x86" download-size="0" install-size="0" version="0.0.0" fragment="true"/> <plugin id="org.mozilla.xulrunner.carbon.macosx" os="macosx" arch="x86" download-size="0" install-size="0" version="0.0.0" fragment="true"/> <plugin id="org.mozilla.xulrunner.gtk.linux.x86" os="linux" ws="gtk" arch="x86" download-size="0" install-size="0" version="0.0.0" fragment="true"/> But I get the following error on fragments, which are not compatible with my current OS: Plug-in reference 'org.mozilla.xulrunner.carbon.macosx' cannot be resolved Plug-in reference 'org.mozilla.xulrunner.gtk.linux.x86' cannot be resolved When editing a target platform definition (Window -> Preferences -> Plug-In Development -> Target Platform -> Running Platform (Active)), I could see only one fragment (which matches my current OS) in the content tab. Then I did the following: Added a "<eclipse-installation>/dropins/xulrunner/eclipse" folder explicitly to the current target platform, pressed "Reload", and voila - other platform-dependent fragments became visible! I think it's a bug. Why platform-dependent fragments are not recognized while being in a context of ${eclipse_home}?
I'm guessing the ${eclipse_home} is only the bundles that are actually installed at that location. The platform specific bundles that don't match will not be installed there even though they are in dropins. Only dropped in bundles that actually match that install and have their dependencies resolved will be installed there.
(In reply to comment #1) > I'm guessing the ${eclipse_home} is only the bundles that are actually > installed at that location. The platform specific bundles that don't match > will not be installed there even though they are in dropins. Only dropped in > bundles that actually match that install and have their dependencies resolved > will be installed there. So, what's the proper way of installing platform-dependent fragments on an existing Eclipse installation, so they become recognizable by feature.xml (and Export product to multiple platforms works as well)?
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.
