on 3/31/02 10:27 AM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
> Why didn't you leave the defaults in place in there? Makes it much easier > to read... I have been through this a bazillion times now on other lists... Essentially, I equate a build.xml to a ./configure. You wouldn't expect someone to cat/more/edit/pico/emacs a ./configure script in order to figure out the defaults, now would you? Why would you expect anyone to look inside a build.xml? With a ./configure, people will ./configure --help to figure out the defaults. If you want to print the defaults, then we should have a <target> that prints out the defaults in a nice format from the default.properties. Just like ./configure --help. Also, to you they are easier to read in the build.xml...to me, they aren't. To me, it is easier to read in the default.properties...to someone else, it may be another way... -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
