Confused about ant api

[Arun]

I'm a bit confused about using the ant api.

All i want to do is select a build file, the directory it must operate
on, and the target that it must operate. I'd also like to get a list of
targets so the user can select one.

So far everything i read requires me to set up various properties etc.
Very confusing.

Anyone got any ideas?

 

[Aquila Deus]

I'm a bit confused about using the ant api.

All i want to do is select a build file, the directory it must operate
on, and the target that it must operate. I'd also like to get a list of
targets so the user can select one.

So far everything i read requires me to set up various properties etc.
Very confusing.

Anyone got any ideas?

Ant is basically a console program, there is no target list or
selector, because GUI is stupid and very diffcult to be controlled by
scripts automatically.

To use ant:
1.write build.xml which defines all targets (and specify one as the
default target), put it under the project's root directory.
2.cd to the directory, run "ant", done!

 

[Oscar kind]

Ant is basically a console program, there is no target list or
selector, because GUI is stupid and very diffcult to be controlled by
scripts automatically.

It's not that a GUI is stupid, but scripts have a very difficult time
talking to it. Most of the time, it's not possible. As to Ant, it doesn't
have a GUI becuse it's not meant to have. It's not meant to be a
standalone tool in a graphical enviromnent:
- For those who use a simple text editor and a command line, a GUI would
be a hindrance: a command line program is much easier.
- For those who have an IDE, a separate tool would be a hindrance: Ant
should integrate into their IDE. This is easy with Ant being a command
line program, but extremely difficult if Ant were a GUI application.

To use ant:
1.write build.xml which defines all targets (and specify one as the
default target), put it under the project's root directory.
2.cd to the directory, run "ant", done!

There is really nothing to add to this. One thiong I did find helpful
though, is finding, copying and adjusting example build files.

 

[Arun]

Sorry i forgot to mention something very stupidly.
I am constructing an ant build file GUI, and i wish to have the
function to run a build file. this is why i need to have an api or
something to use within the gui.

It's not that a GUI is stupid, but scripts have a very difficult time
talking to it. Most of the time, it's not possible. As to Ant, it doesn't
have a GUI becuse it's not meant to have. It's not meant to be a
standalone tool in a graphical enviromnent:
- For those who use a simple text editor and a command line, a GUI would
be a hindrance: a command line program is much easier.
- For those who have an IDE, a separate tool would be a hindrance: Ant
should integrate into their IDE. This is easy with Ant being a command
line program, but extremely difficult if Ant were a GUI application.

There is really nothing to add to this. One thiong I did find helpful
though, is finding, copying and adjusting example build files.


--
Oscar Kind http://home.hccnet.nl/okind/
Software Developer for contact information, see website

PGP Key fingerprint: 91F3 6C72 F465 5E98 C246 61D9 2C32 8E24 097B

B4E2