Bug 90097 - PDE Editor: Unable to Save Changes to Exported Packages in MANIFEST.MF
Summary: PDE Editor: Unable to Save Changes to Exported Packages in MANIFEST.MF
Status: RESOLVED DUPLICATE of bug 87549
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-02 20:02 EST by Simon Archer CLA
Modified: 2005-04-02 20:42 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Archer CLA 2005-04-02 20:02:03 EST
Build: 3.1M6
Build: I20050401-1645

It is possible to get the plugin.xml/MANIFEST.MF editor into a state such that 
it cannot be saved, yet it is still dirty.  The case is pretty strange, so 
please be sure to follow the steps exactly.

1.  Select a plug-in project and open the PDE editor by double-clicking on the
    META-INF/MANIFEST.MF file.

2.  Turn to the Runtime page of the editor.

3.  In the Exported Packages section, click the Add button.

4.  From the Package Selection dialog, select a package and click OK.  The 
    selected package will be added to the Exported Packages list.

5.  The editor will now be dirty, as indicated by the '*' on the editor's tab.
    Do NOT save the editor.

6.  Select the exported package and remove it by clicking the Remove button.
    The selected package will be removed form the Exported Packages list.

7.  As expected, the editor will remain dirty, but it will NOT be possible to
    save the state of the editor.  None of the  menu actions or key sequences 
    to save the editor work.

8.  The only ways to save the state of the editor are as follows:

    a.  Close the editor and answer Yes to the request to save changes.
    b.  Change the state of the editor in some other way, and then save the
        editor using Ctrl+S, File > Save or File > Save All.

9.  When this problem happens nothing is written to the .log file.
Comment 1 Wassim Melhem CLA 2005-04-02 20:42:50 EST

*** This bug has been marked as a duplicate of 87549 ***