[EMAIL PROTECTED] wrote:
On Mon, 8 Jul 2002, Peter Donald wrote:
On Mon, 8 Jul 2002 17:36, [EMAIL PROTECTED] wrote:
See the Ant 2 requirements list.... But on my personal list: - Better expression usage. See Jexl. Access to java objects rather than just flat string properties.
Possible in myrmidon but will never be possible in ant1.x due to backwards compatability.
What has 'backward compatibility' to do with that ?
I actually have a working ProjectHelperImpl for ant1 that supports expersions in ${properties}, using ${lang:expression} style ( lang: is used to locate the evaluator ). I'm trying to integrate JXPath and few
other EL.
The only possible problem may be that someone may have a build file with a variable with that name. However the 'dynamic' properties will
be enabled only by setting a magic property, so the impact is absolutely zero.
Cool! :-)
Keep us informed :-)
If you get this out soon Ant 1.6 will have imports, antlibs, expressions! :-D
I'm also playing ( and is pretty close ) with Axis-style task definitions and expressions - based on namespace. Since Ant1 is not namespace enabled, again there is no backward compat problem - a build file with namespaces can use the new feature, all old files will work the same.
Since this is completely done in the ProjectHelper impl, it doesn't even require changes to ant, will work with ant1.5.
Cool :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
