Return-Path: 
 <dev-return-69732-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 64015 invoked from network); 3 Nov 2005 05:07:40 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 3 Nov 2005 05:07:40 -0000
Received: (qmail 10333 invoked by uid 500); 3 Nov 2005 05:07:39 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 10286 invoked by uid 500); 3 Nov 2005 05:07:38 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 10275 invoked by uid 99); 3 Nov 2005 05:07:38 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2005 21:07:38 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [217.160.128.107] (HELO www.samaflost.de) (217.160.128.107)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2005 21:07:33 -0800
Received: by www.samaflost.de (Postfix, from userid 1000)
	id 50AE288A36A; Thu,  3 Nov 2005 06:07:15 +0100 (CET)
To: dev@ant.apache.org
Subject: Re: XmlProperty
X-Draft-From: ("nnfolder:mail.jakarta-ant" 71480)
References: <20051102220320.87375.qmail@web30907.mail.mud.yahoo.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: Thu, 03 Nov 2005 06:07:15 +0100
In-Reply-To: <20051102220320.87375.qmail@web30907.mail.mud.yahoo.com> (Matt
 Benson's message of "Wed, 2 Nov 2005 14:03:20 -0800 (PST)")
Message-ID: <87zmomnwu4.fsf@www.samaflost.de>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On Wed, 2 Nov 2005, Matt Benson <gudnabrsam@yahoo.com> wrote:
> --- Stefan Bodewig <bodewig@apache.org> wrote:

>> Hmm, I'd prefer (ab?)using PropertyHelpers for this
>> instead of adding
>> new helpers.
>> 
>> <copy resource="${resource:url:someurl}"/> or
>> something similar.
> 
> Hmm... this appears doable... it will require that the
> properties be resolved by IntrospectionHelper instead
> of RuntimeConfigurable though, which could require the
> usual backwards-compatibility acrobatics.

Do we really need to resolve that in IntrospectionHelper?  Why?

> The resource-aware PropertyHelper would become part of the default
> PropertyHelper chain then as well?

Yes.

> Speaking of which we still need to make adding
> PropertyHelpers to the chain more (at all)
> user-friendly, but that's (yet) another discussion.

I agree, maybe providing a task that does (same for InputHelper or the
Executor).

>> You have no idea what type of odd ideas I have for resource
>> collections 8-)
> 
> Please, go ahead.  Scare me!

Something I've been meaning to propose for two years but never had the
time to fully think through.  Allow each task to take input in form of
a ResourceCollection and to declare its output as a ResourceCollection
as well.

Using this, provide a <pipe> task that chains the output of task n to
the input of task n+1, something like

<pipe>
  <javac .../>
  <jar .../>
</pipe>

where jar would update an archive with the output of the javac task
(no idea whether this is useful).

More interesting, make targets have input and output - the input is
passed to the first task, the output provided by the last task in the
target.  Extend this to a whole project as well.

With this, <ant buildfile="projectA.xml"/> would provide the build
artifacts of projectA as outputs.  Let's say projectA creates a jar
that my current project depends on, then I can add the <ant> task's
output to a path to use it in <classpath> settings, or I can copy it
around.

My main goal here is to make projects less strongly coupled, I only
need to know that I need the jar created by projectA, I don't need to
know where it ends up or how it is called.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org