Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 14611 invoked from network); 20 Feb 2002 07:48:50 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 20 Feb 2002 07:48:50 -0000 Received: (qmail 6479 invoked by uid 97); 20 Feb 2002 07:48:59 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 6425 invoked by uid 97); 20 Feb 2002 07:48:58 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 6414 invoked from network); 20 Feb 2002 07:48:58 -0000 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: Official direction for xdocs References: <3C6E4B12.7060703@yahoo.com> <3C722F6E.60304@yahoo.com> From: Stefan Bodewig Date: 20 Feb 2002 08:34:38 +0100 In-Reply-To: <3C722F6E.60304@yahoo.com> Message-ID: Lines: 63 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 19 Feb 2002, Paul Hammant wrote: > I'm talking of a position a year ago, when the doanloadable ant > could not use , xml.apache.org jars had to be downloaded > and a recompile or optional.jar issued. As Ant would pick up all jars from ANT_HOME/lib, no recompiled optional.jar, just an additional jar that contained the stylebook task would be necessary. But I'm picking nits. > It seems odd to me that many of the major projects at Apache have > xdocs, but there is no way of using the downloaded ant via ANT_HOME > to completely build the project. First, which tool to use is a religious issue - and I think Ant is better of when it doesn't take any position here. Of the several options to convert xdocs to HTML, all could be done with single downloads, but I don't think they should bundle with Ant. In the case of Anakia, it would be easy to create a download that contained the required versions of Velocity and JDOM together with a jar that contains the task definition itself - three jars and the installation instruction is "put these jars into ANT_HOME/lib". In the case of Stylebook, things would be even easier. "put stylebook.jar into ANT_HOME/lib" and assume that people use the optional.jar from our distribution area, which contains all optional tasks, including the stylebook task. I think my main point is that IMHO it is the responsibility of the projects that offer XML -> HTML conversion via Ant to provide the single stop download. And I'd really prefer if they would not bundle Ant but assumed that Ant was already installed (and point the people to the latest release of Ant). This may mean two downloads for some people, but in many cases Ant will have been in use as a build tool before people thought about creating HTML from XML using Ant. > Avalon "solves" the issue by keeping in its tree its own version of > Ant. Why? > In that ant we have stuffed many other jars. Just put these other JARs into the CLASSPATH or ANT_HOME/lib, no need to include Ant itself. > Nikola Barrozi has an excellent Ant using "starter project" for > third parties called Centipede. Do you have a pointer? Sounds as if we should link to it from our site. > Like Cocoon's build files it is well separated, but building in a > custom version of Ant with Cocoon in it. I don't get it. Why not simply ship the additional classes in a jar of its own and rely on a proper installation of Ant. Ant is in such widespread use that you can almost assume an Ant installation when dealing with Java projects, Stefan -- To unsubscribe, e-mail: For additional commands, e-mail: