Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335998 - Ant builder Edit Configuration dialog shows wrong selected targets after editing
Summary: Ant builder Edit Configuration dialog shows wrong selected targets after editing
Status: CLOSED DUPLICATE of bug 114563
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-01 13:29 EST by Markus Keller CLA
Modified: 2011-02-02 14:28 EST (History)
2 users (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 Markus Keller CLA 2011-02-01 13:29:40 EST 
I20110127-2034, found when trying to remove a workaround for bug 114563

I'm not sure I fully understood when the 4 target tasks selected in the Ant builder Edit Configuration dialog are supposed to be executed. I didn't find anything in the help about this. Bug 87697 has a longer discussion about these tasks, but I'm not sure if that's the latest word.

Anyway, a bug I see in the UI is this:

- select nothing for 'After a "Clean"' target
=> value becomes <Builder is not set to run for this build kind>
- click OK, edit same builder again
=> value is <default target selected>

Please have a closer look at this before backporting bug 114563.
Comment 1 Markus Keller CLA 2011-02-01 13:30:59 EST 
Filed bug 335999 for the missing documentation.
Comment 2 Michael Rennie CLA 2011-02-01 14:06:31 EST 
(In reply to comment #0)
> Please have a closer look at this before backporting bug 114563.

*sigh*, "no builder" and "default" are both null in the configuration, and now that FULL is added to the build kind listing clean always thinks it is selected.
Comment 3 Michael Rennie CLA 2011-02-02 14:28:09 EST 
Looking more at the cause of this, I am going to reopen bug 114563, and mark this as dupe of that one, reason being it is caused by that fix, and an updated fix to 114563 will not cause this problem.

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