Community
Participate
Working Groups
I changed the value of the featureName/pluginName/providerName in the feature.properties and plugin.properties files and noticed that the feature information on Installation Details is not retrieved from feature.properties. Problems: 1) feature provider name is retrived from plugin.properties 2) feature name is retrived from plugin.properties 3) "NLS" feature provider name is retrived from "code" plugin.properties 4) "NLS" feature name is retrived from "code" plugin.properties Problem 1 may not be too bad as the feature provider is usually the same as the plugin provider. Problem 2 may be a little problem if the plugin name is not generic and contains the word "plugin". Problems 3 & 4 are more serious problems. We are not showing the correct provider name and feature name when an adopter is providing the "NLS" feature. Expected results: - I expect the Installation Details dialog to retrieve the feature provider name and feature name from the feature.properties file of the corresponding feature.
Created attachment 169691 [details] Installation Details
moving to p2. Installation Details info comes from the p2 metadata. The metadata generation tools do some kind of mapping, not sure if there is a bug here or not...
Kit could you please verify what happens on 3.4? I don't think much changed in this space since then. Also at this point this information is not read from the p2 metadata but from the feature folder / feature.xml and other files.
This is not a new problem. I confirmed that it was the same way in Eclipse 3.4.2. I just noticed where the strings are coming from by changing the value of the featureName/pluginName/providerName strings in the feature.properties and plugin.properties files.
Created attachment 170213 [details] Linux Tools screenshot Here's a similar example with Linux Tools.
*** Bug 315598 has been marked as a duplicate of this bug. ***
*** Bug 315601 has been marked as a duplicate of this bug. ***
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.
