Hi,
Applied - thanks.
I made a couple of modifications:
* Use Avalon's Context instead of PropertySet interface. Doesn't really
seem worth adding yet another 'find this object by key' interface, at least
for the time being. Context is close enough. We need to address the fat
TaskContext vs a map of objects issue in a few other places as well, so
let's hold off on PropertySet. Unless you see PropertySet evolving into
something more than a single lookup method?
* ClassicPropertyResolver returns ${propname} for undefined properties,
rather than an empty string. This is how Ant 1 behaves.
Adam
> -----Original Message-----
> From: Darrell DeBoer [mailto:[EMAIL PROTECTED]
> Sent: Friday, 8 March 2002 11:29 PM
> To: [EMAIL PROTECTED]
> Subject: [myrmidon] PATCH: PropertyResolver service.
>
>
> Hi,
>
> The supplied patch addresses the TODO item:
> "Convert PropertyUtil to a non-static PropertyResolver service."
>
> Change details:
> * Added PropertyResolver service interface, together with 2
> implementations.
> (One implementation mimics Ant1 behaviour). These are added in the
> "workspace" packages, since that's where PropertyUtil was. Not
> sure if this
> is the right place.
> * DefaultTaskContext now implements PropertySet interface, used by
> PropertyResolver. This avoids having the PropertyResolver dependent on
> TaskContext, avoiding a potential circularity problem. (since
> TaskContext has
> a "resolve" method of it's own).
> * Removed PropertyUtil.
> * Tests for PropertyResolver implementations.
> * Minor fix for aut.nativelib.Os.java: "dos" family was
> incorrectly included
> in the "windows" family.
>
> There seems to a problem with the current Myrmidon build. Included in the
> patch is a fix to build.xml which overcomes this. However, this
> is probably
> only a temporary work-around, and maybe should be omitted from
> the commit.
> (At least it let's me run the tests ;) )
>
> Thanks,
> Daz
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
