This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 23776 - Cannot change order of depends targets
Summary: Cannot change order of depends targets
Status: VERIFIED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: -FFJ-
Hardware: All All
: P4 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on: 42859
Blocks:
  Show dependency tree
 
Reported: 2002-05-21 13:36 UTC by Milan Kubec
Modified: 2005-12-20 16:04 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

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 Milan Kubec 2002-05-21 13:36:15 UTC 
User should be able to change order of targets
which another target depends on. Some kind of
reorderable list of checkboxes.
Comment 1 Jesse Glick 2002-05-21 19:09:36 UTC 
Last I checked on ant-dev@jakarta.apache.org, the order of targets in
a depend="..." attribute is not specified to mean anything. Thus the
NB UI is consistent in not providing reordering support for it.
Comment 2 Quality Engineering 2003-06-30 14:44:34 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 3 Quality Engineering 2003-06-30 14:47:30 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 4 Jesse Glick 2004-03-30 15:18:52 UTC 
Apologies - the Ant manual does say that it will attempt to honor the
supplied order (though it may be modified by dependencies).
Comment 5 Jesse Glick 2004-03-30 15:19:50 UTC 
Really no plans to implement more Explorer-based GUI however, unless
there is proper XML structure editing support.
Comment 6 Jesse Glick 2004-05-05 16:20:22 UTC 
No longer plan to support structure editing.
Comment 7 Marian Mirilovic 2005-12-20 16:04:53 UTC 
This issue was solved long time ago. Because nobody has reopened it neither
added comments, we are verifying/closing it now. 
If you are still able to reproduce the problem, please reopen. 

Thanks in advance.