ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: XmlProperty
Date Thu, 03 Nov 2005 05:07:15 GMT
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


Mime
View raw message