Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345717

Summary:	Adding plugin activator does not work in case of another action on the Activator is taken
Product:	[Eclipse Project] PDE	Reporter:	Vladislav Iliev <vladislav.iliev>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	Michael_Rennie, vladislav.iliev
Version:	4.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Vladislav Iliev

2011-05-13 07:16:49 EDT

Build Identifier: I20110310-1119

When creating activator in a plugin project via the Manifest editor the activator class is opened asking for an import of some packages. After importing the rqeuired packages the "Bundle-Activator" header in the manifest file is removed.

Reproducible: Always

Steps to Reproduce:
1. Create new plugin project via File->New->Plugin Development->Plug-ing project
2. Don't create an activator (deselect the checkbox "Generate an activator, a Java class the controls the plug-in's lifecycle)
3. Open generated MANIFEST.MF file (should be opened via Manifest editor).
4. In section "General information" click on "Activator" link to create an activator. New java class wizard appears.
5. Enter needed information -for example enter only the class name - Activator1
and click on button Finish. The Activator1.java class should be opened for edit.
6. Import of org.osgi.framework.BundleActivator is not recognized, that's why
via quick fix select "Add 'org.osgi.framework'" option.
7. Again via quick fix, put some implementation for required methods (start,stop)
8. Open Manifest.mf file via text editor.
Expected: There must be a header "Bundle-Activator"
Actual: The header "Bundle-Activator" is missing.

Comment 1 Eclipse Genie

2019-05-25 15:32:58 EDT

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.