Return-Path: <bodewig@apache.org>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 31946 invoked from network); 30 Jan 2001 09:47:39 -0000
Received: from bodewig.bost.de (root@195.227.98.11)
  by h31.sny.collab.net with SMTP; 30 Jan 2001 09:47:39 -0000
Received: (from bodewig@localhost)
	by bodewig.bost.de (8.9.3/8.9.3) id KAA01773;
	Tue, 30 Jan 2001 10:47:51 +0100
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@apache.org using -f
To: ant-dev@jakarta.apache.org
Subject: Re: Proposal for a new task <xslt> (different semantics than <style>)
References: <003501c08b0a$7ea9e090$e7c0a1c3@vismech.ru>
From: Stefan Bodewig <bodewig@apache.org>
Date: 30 Jan 2001 10:47:51 +0100
In-Reply-To: "Ivan Mikushin"'s message of "Tue, 30 Jan 2001 14:17:50 -0800"
Message-ID: <m3puh5id6g.fsf@bodewig.bost.de>
Lines: 38
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Ivan,

the <style> task has changed quite a bit since Ant 1.2. I'm not sure,
but I think it already addresses a couple of your points.

Ivan Mikushin <ivan@vismech.ru> wrote:

> - one may need to specify XSLT transforms not bound to basedir for
> the <style> task instances

<style> now has in/out parameters for situations like this.

> - one may need to supply parameters to an XSL transform

<style> has a nested <param>.

> - <style> has a redundant attribute 'processor' which is unneeded
> when TrAX interfaces (seems to become standard) are used

I think we should not drop Xalan1 support right now. <style> now also
supports a TrAX processor which may very well become the only major
option in the long term.

> - XSLT transforms are not necessarily used for styling: you may use
> it to generate code, and whatever, so it's reasonable to name the
> task <xslt> and to indicate XSLT file with 'transform' attribute.

Agreed, we could alias it to be called in both ways and deprecate
<style> if we all agree on that. This is much the same way <expand>
has been renamed to <unzip> a while back.

> I rewrote XSLTProcess class (mine is named XSLTProcess2) to meet
> these issues (actually took XSLTProcess and changed it a little).

I'd ask you to take a look at the version of <style> in CVS and merge
in whatever functionality is missing from your implementation.

Stefan