Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <avalon-dev@jakarta.apache.org>
Message-ID: <3C74F57B.6030809@yahoo.com>
Date: Thu, 21 Feb 2002 13:26:19 +0000
From: Paul Hammant <Paul_Hammant@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:0.9.7) Gecko/20011221
MIME-Version: 1.0
To: Avalon Development <avalon-dev@jakarta.apache.org>
Subject: Ant
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Folks,

We have a built in Ant.  I have come to the conclusion that it does not 
help us re acceptance.  Newbies fear the scope of what we might have 
done to Ant and why we would want to.

I think we have our own ant primarily for xdoc generation (a subject 
some of you may note I raised in the Ant list).  These are the jars we 
have placed in the ext/ dir that take us away from a standard Ant 1.4.1 
...  Cocoon is for xdocs,  fop & batik are for the PDF output.

  avalon-excalibur.jar
  avalon-framework.jar
  batik-libs.jar
  cocoon.jar
  fop-0.20.2.jar
  jimi-1.0.jar
  logkit.jar
  resolver.jar

What would people say about the desirability of purging the built-in Ant 
completely?  What are the technical reasons why we may not be able to do 
this?

Regards,

- Paul H


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>