Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 137383 - [launching] [LCD] revert button does not work as expected
Summary: [launching] [LCD] revert button does not work as expected
Status: RESOLVED DUPLICATE of bug 147044
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5   Edit
Assignee: Darin Swanson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-18 17:40 EDT by Michael Rennie CLA
Modified: 2009-05-06 13:55 EDT (History)
0 users

See Also:


Attachments
patch for revert button (15.55 KB, patch)
2006-06-15 09:44 EDT, Michael Rennie CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2006-04-18 17:40:20 EDT
If you make a change to a ant launch configuration and hit 'revert' it reverts the change but does not disable the revert or apply buttons. This is because the ant tabs are telling the LCD that they are still dirty even after a revert (apply works fine). 

The problem is in the size of the attribute maps between the original and the working copy. For some reason after a revert the original contains the attribute 'org.eclipse.jdt.launching.JRE_CONTAINER', whereas the working copy does not.

To reproduce:
1. open the LCD in external tools mode
2. select and edit an attribute on an ant tab
3. hit the revert button
Comment 1 Darin Swanson CLA 2006-04-20 13:14:40 EDT
I believe a regression introduced from the fix for bug 107721.
Testing a tentative fix...
Comment 2 Darin Swanson CLA 2006-05-10 00:24:21 EDT
Deferred to 3.3
Comment 3 Michael Rennie CLA 2006-06-15 09:44:07 EDT
Created attachment 44516 [details]
patch for revert button

try this to fix the issue...
Comment 4 Darin Swanson CLA 2006-06-15 12:29:31 EDT
Thanks Michael...I will check it out.
Comment 5 Michael Rennie CLA 2009-05-06 13:55:54 EDT
the updated patch for bug 147044 fixes this issue as well, marking as a dupe of 147044

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