Bug 26755 - Ant problems
Summary: Ant problems
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: core, ui
Depends on:
Blocks:
 
Reported: 2002-11-20 07:30 EST by Thomas Eichberger CLA
Modified: 2002-11-26 13:08 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 Thomas Eichberger CLA 2002-11-20 07:30:58 EST
I found a few problems with running Ant from within Eclipse 2.1.
Build ID 200211151436

I couldn't start Ant with the build.xml. I renamed build.xml to another name,
then renamed it back to build.xml and now it worked.

External Tools View: the configuration menu
Options -> Prompt for arguments before running tool
does not work.
Or how do I configure that I want to choose the targets that should run? Eclipse
Ant never asks me now in M3, in earlier versions it did.

Window -> Preferences -> External Tools -> Ant -> Classpath
When I add a file to this Ant classpath, it is not remembered after leaving and
starting Eclipse again.

I have a target which fails if there is not user property assigned by
ant -Duser=whoever
This target works when I start it from a prompt window. In Eclipse I had
External Tools View -> click on build.xml right mouse -> properties -> Arguments
- and in this text field I wrote   -Duser=whoever
Doesn't work, the target always fails - 
That's the first question, how to insert a -D property.

And - second point - when I start that target by right clicking on build.xml in
the Package Explorer, I get a dialog which gives me my error message in the fail
part of the target.
But when I start it with Run -> External Tools -> build.xml I get no error dialog?

I've read that Ant in Eclipse will be changed a lot until the next version, so
maybe all those things are just temporary problems, but they are very disturbing
nevertheless.
Comment 1 Darin Swanson CLA 2002-11-26 13:08:56 EST
Most of these problems have been addressed by other bug reports and with the 
new development. The remaining use cases are no longer possible.
Sorry for the problems but things are changing really rapidily in the external 
tools / Ant integration.
I am going to close this bug report but please if you can evaluate the latest 
integration build (coming out today) and open separate bug reports for any 
problem that still exists.