Hello Jesse,
when someone is developing ant inside an IDE, I believe that the
IDE's default functionality is good enough to work, because ant is
for the most part a java library.
you can modify ant classes in the IDE, then run the corresponding
JUnit tests, and you do not need all the bootstrap scripts etc to do
that.
Regards,
Antoine
On Aug 30, 2006, at 4:31 AM, Jesse Glick wrote:
Stefan Bodewig wrote:
Sometimes we build new features that are useful enough to apply the
right away in Ant's own build file.
Obviously. But it seems to me that the convenience of the many
users of Ant (sources) outstrips the convenience of the few Ant
developers. For example, it is impossible to develop the Ant trunk
in NetBeans using the bundled Ant 1.6.5 unless you write a wrapper
script which execs bootstrap.sh, which is unpleasant. Similarly you
could not use a bundled Ant binary on Linux to run ant/build.xml
targets (or use Bash completions...).
To Jan: I meant only keeping compatibility with the previous
official Ant release, in this case 1.6.5.
To Kev: surely most Ant committers work on at least one other Ant-
based project where improvements can be seen? Or does the Apache
Foundation pay your rent? :-)
Just wondering why an Ant release is expected to be used by many
thousands of Java programmers for every purpose you can think of,
yet it's not good enough for Ant itself which is a pretty small
project. I don't feel strongly about it though.
-J.
--
[EMAIL PROTECTED] x22801 netbeans.org ant.apache.org
http://google.com/search?q=e%5E%28pi*i%29%2B1
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
