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

Bug 448278

Summary: Add property page to feature projects to resolve problem of "Recompute checkbox's old state not retained on import".
Product: [Eclipse Project] PDE Reporter: pragya gaur <pragya.g>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: karsten.thoms
Version: 4.5Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description pragya gaur CLA 2014-10-22 05:59:47 EDT 
In the feature.xml editor, on top of Dependencies tab there is one check box labeled:

Recompute when feature plug-ins change

You can tick it and save, but if the feature project is exported and then imported at different workspace, the information of the checkbox being checked is getting lost.

Reproducible: Always

Steps to Reproduce:
1. Open feature.xml
2. Click Dependencies tab
3. Tick "Recompute when feature plug-ins change"
4. Save and close feature.xml
5. Export the feature project.
6. Import the exported project in different workspace.
7. Open feature.xml and go to Dependencies tab, the checkbox is unchecked.

The Delux solution for the above problem as suggested by Curtis Windatt( cwindatt@ca.ibm.com) is to add a property page to feature projects, similar to the 'Plug-in Development' page on bundle projects.  The user could have an option 'Always recompute '.  That setting would be stored in the .settings folder of the project, so when it is in SCM, others would get the setting for free. The option in the feature editor would be associated with that preference.

Note that you can open a feature.xml outside of a project (File > Open) so we should check that we handle that case.
Comment 1 Eclipse Genie CLA 2019-10-07 03:56:16 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.