Hi Christoph,

I don't want anything fancy or graphical or complicated at all. When I'm
working with ant, I spend a lot of my time editing build.xml.  Now, I can be
in any directory when I want to edit it, so sometimes I do this:

vi ../../../../../build.xml

and sometimes I do

vi ../../build.xml.

Now, I know I could do something like

vi $BUILD_HOME/build.xml

or I could even write a shell alias to do what I want.  But it just seemed
more generally useful if I could do something like

ant -edit

and that would locate the build.xml file and launch vi for me to edit it.
Could do it with a very simple piece of scripting in the ant shell script,
or you could do it in the java code itself.  I am not talking about IDEs or
anything like that, just a convenient little option that I would find
personally useful.

Cheers,
Mike.

> -----Original Message-----
> From: Christoph Wilhelms [mailto:[EMAIL PROTECTED]
> Sent: 07 April 2001 03:00
> To: [EMAIL PROTECTED]
> Subject: RE: Feature suggestion
>
>
> Hi!
>
> Can you please tell me, if I understood correctly what you want!
>
> Do you want to run commandline Ant everywhere, poping up a FileSelector if
> "build.xml" cant be found? If so, then you shouldt start Ant, but
> Antidote,
> for it is capable of it ATM!
>
> Otherwise, If you want to modify the projectdefinition while ant
> is started
> Antidote is the rightone, too - even there is still a litte bit missing...
> but we are workig on it (mostly Sim and Nick :-))!
>
> Greetigs,
> Chris
>
> > Mike,
> >
> > IMHO, I do not see that as a core ant feature. It is really
> something that
> > Antidote will offer and  is more appropriate there where you
> will have an
> > "integrated" environment.
> >
> > Conor
> >
> > > How about adding a feature to ant that allows editing of the build.xml
> > file:
> > >
> > > "ant edit" locates the build.xml file and kicks off an editor using a
> > > specified command line.  Saves having to go looking for the build.xml
> > file
> > > everytime you want to edit it.
> > >
> > > Cheers,
> > > Mike.
>
>

Reply via email to