From: Jason Petrone <jpetrone@cnri.reston.va.us>
To: Anthony Green <green@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: Ant
Date: Mon, 22 Oct 2001 13:09:00 -0000 [thread overview]
Message-ID: <20011022160206.E31727@cnri.reston.va.us> (raw)
In-Reply-To: <003501c15b26$13dcb200$5be6b4cd@cygnus.com>
On Mon, Oct 22, 2001 at 11:19:23AM -0700, Anthony Green wrote:
> Jason wrote:
> > Any plans to add ant( http://jakarta.apache.org/ant/ ) to RHUG?
> Well, I'm not sure exactly what the value would be.
I use ant as a build tool for java programs. I get really frustrated by its
startup time and wish it was a native program. Right now I'm running it
from a special shell that only loads it once, but this is really a hack.
Only loading the compiler code once is only one small reason for using ant,
the main reason I use it is for its java dependency generation. And it can
use jikes instead of the normal compiler, which means it wouldn't be any
slower under native code.
> Don't let this stop you though!
Ok, this is what I wanted to hear...
Thanks.
jason
next prev parent reply other threads:[~2001-10-22 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 10:39 Ant Jason Petrone
2001-10-22 11:13 ` Ant Anthony Green
2001-10-22 13:09 ` Jason Petrone [this message]
2001-10-23 10:53 ` Ant Alexandre Petit-Bianco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011022160206.E31727@cnri.reston.va.us \
--to=jpetrone@cnri.reston.va.us \
--cc=green@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).