On 11/6/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
On Mon, 6 Nov 2006, Kevin Jackson <[EMAIL PROTECTED]> wrote:
> Having a free afternoon today and spotting
> http://issues.apache.org/bugzilla/show_bug.cgi?id=28941
>
> in bugzilla, I think it would be a good idea to follow up with the
> suggestion to add something like it to the tasks.
+0
I once hoped I could supersede functionality like this with something
similar to MSBuild's Items. Some tasks create items, which are simply
references to ResourceCollections, some would accept them as input and
some would do both. I started a proof of concept implementation
almost three years ago (using path instead of resource collection) but
never came around to making it useful.
Such a "task pipeline" is much more ambitious (and interesting as a
concept). But here we're only talking about extracting information
from a task post-execute(), kinda similar to the errorproperty of
forking tasks.
A generic mechanism for "asking questions" to tasks (or beans in
general) could use ids and introsespection (a kind of IH in reverse,
operating on getFoo rather than setFoo methods), but again it's much
more than adding a compiledCount attribute to <javac>, and something a
scripting language rather than Ant should do probably. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
