Bug 17406

Summary: [ExternalTools] Ant default target should be "main"
Product: [Eclipse Project] Platform Reporter: Adam Schlegel <Adam_Schlegel>
Component: AntAssignee: Ryan Cooper <ryan_cooper>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: rodrigo, simon_arsenault
Version: 2.0Keywords: ui
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Adam Schlegel CLA 2002-05-23 13:05:38 EDT
If the 'default' atribute of the 'project' tag is not specified, then it should 
revert to 'default=main'. (see online Ant Documentation at 
http://jakarta.apache.org/ant/manual/index.html)

Currently Ant complains that the 'default' attribute is required.

Is this a change in Ant's behaviour between version 1.4.1 (in Eclipse), and 1.5 
(in the Documentation)?
Comment 1 DJ Houghton CLA 2002-05-23 16:43:13 EDT
Investigate for 2.0.
Determine if this is a 1.5 only thing.
Comment 2 Rodrigo Peretti CLA 2002-05-28 13:07:04 EDT
Comparing the docs it seems new to 1.5. In 1.4.1 the default target is 
mandatory in the project declaration. In 1.5 it is not mandatory anymore and 
if ommited the default should be set to main.

Moving to Platform UI for comments. It affects they way we extract information 
to populate the Ant Wizard. My suggestion is to allow flexibility.

1) If the default is not set do not throw any errors (I believe the user will 
get an error later on if using 1.4.1 and will be OK if using 1.5).

2) If the default is not set and there is NO "main" target. Same as (1).

3) If the default is not set and there is a "main" target. Set the default 
target to be main.
Comment 3 Simon Arsenault CLA 2002-05-30 14:00:04 EDT
We already do 1 & 2. We can handle 3 in the validateDefaultTarget method.
Comment 4 Simon Arsenault CLA 2002-07-15 12:57:08 EDT
Looking at the documentation that ships with the 1.5 release of Ant, 
the "default" attribute is still required. It seems what Adam saw was part of a 
beta of 1.5

Closing this PR. Please reopen if you can find the appropriate documentation in 
release 1.5 (or from their mailing-lists/newsgroups).