Community
Participate
Working Groups
Build Identifier: 3.6 Getting this error message ( Plug-in Problem) Plug-ins declaring extensions or extension points must set the singleton directive to true While my bundle does not define any extensions, or extension point. And I was unable to get rid of this error, except by deleting the plugin.xml which was not intuitive. Reproducible: Always Steps to Reproduce: 1. In a Bundle Manifest Editor, click on the Extensions tab. 2. Click the Add... Button to add an Extension. 3. Then Cancel this dialog ( so no extensions were added) 4. I get an Error ( Plug-in Problem) Plug-ins declaring extensions or extension points must set the singleton directive to true
Isn't there a quickfix to delete the plugin.xml since it's useless?
There is no way this is major in anyway btw ;)
I get an error and a warning both with quickfixes. 1) The Error is complaining that my plugin should be a singleton, Quickfix: Adds the singleton directive to the bundle Manifest. 2) The warning is complaining that my plugin.xml need to have at least one extension defined. Quickfix: delete the plugin.xml file, or add extension. Executing the quickfix to delete the file did delete the plugin.xml Usually users would start by cleaning the errors, so they would end up with the singleton added to their Manifest. I suggest that for the error quickfix, find if the plugin.xml does not define any extension is to offer to delete the plugin.xml
The manifest and plugin.xml builders run separately, so when we create the singleton marker we do not know what problems exist in the plugin.xml.
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.
