Community
Participate
Working Groups
Extension point definitions that don't define their own namespace (only an option on schema version 3.2+), take the namespace of the bundle. When the bundle is refactored, we currently don't update any of these extension references that would break. For example if a plug-in named "com.ibm.plugin" has an extension "coolStuff", all references to this extension will be in the form of "com.ibm.plugin.coolStuff". When the plug-in is refactored to "org.eclipse.plugin" all the references to com.ibm.plugin.coolStuff will break since the extension point is not "org.eclipse.plugin.coolStuff". It would be nice to update these references when we refactored a bundle's id.
Tagging bugday and adding context.
Created attachment 84277 [details] mylyn/context/zip
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 worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
