ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16867] - Ant + Windows = Ant doesn't work and is incompatible because WIndows command line sucks and ANt developers didn't take that into account
Date Fri, 07 Feb 2003 20:02:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16867>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16867

Ant + Windows = Ant doesn't work and is incompatible because WIndows command line sucks and
ANt developers didn't take that into account





------- Additional Comments From blackened@austin.rr.com  2003-02-07 20:02 -------
Nope, I wouldn't expect you to improve Windows or include an Ant-specific
service pack for Windows with Ant, that's silly.  But when your program doesn't
work, or when a user cannot see output, I think you have a serious problem. 
Imagine if you wrote a Windows application that only ran at a resolution of
1280x1024 and announced to the world that anyone with Windows can run it!  But
when users downloaded it, some of them realized they couldn't run it because it
was made to run at only 1280x1024.  Well, I would say that's a serious flaw with
your software, and unless there was a really good reason for forcing 1280x1024
resolution for your software, it's probably a dumb idea.  

Excuse the crappy analogy, but nonetheless, I think it applies.  If you write an
app for Windows but don't take into account the limitations of Windows, you're
setting yourself and your users up for trouble.  Trust me, I'm not trying to
bash Ant, I know you guys wrote some code that I'm able to download for free and
play with, so obviously if I don't like it, you have no obligation to support
me.  It was simply a recommendation, that if you're going to design a program
for windows that's dependent on the evil MSDOS Command Prompt, then either
adjust the output of Ant so that it accomodates this limitation, or provide some
links or something to some software that will enable Ant to run a little more
gracefully under Windows.  In my case, I was running ant, but getting an error
message that I couldn't understand because it was beyond the border of my
command prompt.  That's a serious problem for Windows users running Ant.  In
most cases piping output or doing |more will work, but in this case, it didn't.
 For whatever reason, I guess stderr doesn't pipe to the more command.

So don't take it as me bashing your software, but instead read it as me making a
recommendation as a frustrated user.  I know Windows sucks for things like this,
and it must be a real headache, I sympathize.  But nothing would be better than
to have Ant performing as the most robust build system on all platforms.

Thanks again for all the recommendations, and continue the good work.

-Dustin

Mime
View raw message