Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317404 - NewPluginProjectFromTemplateWizard: set check at Activator button depends on content wizard configuration
Summary: NewPluginProjectFromTemplateWizard: set check at Activator button depends on ...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-21 04:40 EDT by Alexey Markevich CLA
Modified: 2019-09-09 02:21 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Markevich CLA 2010-06-21 04:40:09 EDT 
I have content wizard described as
   <extension
         point="org.eclipse.pde.ui.pluginContent">
      <wizard
            ...
            requiresActivator="false">
      </wizard>
and create them using NewPluginProjectFromTemplateWizard.
Options at first page set correcly (because wrapper class NewProjectCreationFromTemplatePage used), but at second page (PluginContentPage instance) Activator generation checkbox already checked even set to false in extension point.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:13:15 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.
Comment 2 Julian Honnen CLA 2019-09-09 02:21:42 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.