Community
Participate
Working Groups
Build Identifier: I20100429-1549 1. Create a FeatureA with PluginA and add FeatureA to dropins. Start Eclipse. ReconcilerProfileChangeRequest: ==Profile change request for SDKProfile ==Additions== PluginA 1.0.0.201005271557 content.xml and artifacts.xml files generated during installation are attached in FeatureAInstallationRepositories. 2. There is no FeatureA in "What's already installed" view but PluginA can be seen in Plug-in registry view. 3. Shut down Eclipse. Create FeatureB with PluginB and add to dropins. Start Eclipse. ReconcilerProfileChangeRequest: ==Profile change request for SDKProfile ==Additions== FeatureA.feature.group 1.0.0.201005271557 FeatureA.feature.jar 1.0.0.201005271557 PluginB 1.0.0.201005271607 content.xml and artifacts.xml files generated during installation are attached in FeatureBInstallationRepositories. 4. Now there is FeatureA in "What's already installed". But there is no FetaureB. PluginA and PluginB can be seen in in Plug-in registry view. Why only plugin from the feature is installed firstly? Why feature itself is installed during next modification of configuration? Is this designed to work this way? Reproducible: Always
Created attachment 170190 [details] content.xml and artifacts.xml created for dropins operations
I am unable to reproduce this problem locally using a 3.6 build from this week on WinXP. I am creating a single feature with a single plugin and putting them in dropins/features and dropins/plugins and everything is installed fine on first startup and the feature appears in the Help -> About. Can you attach the features/plug-ins that you are installing along with specific details to the paths you are putting them in the dropins? Thanks.
Created attachment 170309 [details] dropins FeatureA and FeatureB attached. They are placed in: eclipse/ dropins/ FeatureA/ features/ plugins/ FeatureB/ features/ plugins/
This issue seems to be a little bit random - during tests I've observed that sometimes it works correctly and feature is installed at the first attempt. But here are scenarios that repeat with vanilla eclipse-SDK-3.6RC1-win32: Scenario 1. download eclipse-SDK-3.6RC1-win32.zip and extract start stop start stop (to be sure that all initial reconciliation is done) add feature to dropins start only plugin is installed stop start again feature still not present, only plugin can be seen Scenario 2. download eclipse-SDK-3.6RC1-win32.zip and extract before start add feature to dropins start only plugin is installed stop start again feature installed Issue with second reconciliation may have meaning here... Bug 313905
The bundles/features that you attached are from an update site. That is, the features are in JAR form rather than runnable/expanded form and the metadata matches this. This is not a supported format for the drop-ins folder. If you expand the features into runnable form and remove the metadata (to allow the publisher to re-generate it) then everything will be installed correctly on the first start-up.
