Ivy release?

2009-09-04 Thread Maarten Coene
Hi all, the second release candidate for Ivy is now some weeks old and it's time we decide what to do next. I'd prefer to promote this RC2 as final 2.1.0 release, but merge revision 801820 from trunk which fixes a regression introduced in RC2. Furthermore, since trunk contains fixes for some an

Re: How about ${fromRefId:some-reference}?

2009-09-04 Thread Matt Benson
You might also want to check out the refs and types evaluators from the props antlib here... they're a little generic though. -Matt --- On Fri, 9/4/09, Stefan Bodewig wrote: > From: Stefan Bodewig > Subject: Re: How about ${fromRefId:some-reference}? > To: dev@ant.apache.org > Date: Friday,

Re: How about ${fromRefId:some-reference}?

2009-09-04 Thread Stefan Bodewig
On 2009-09-04, Dominique Devienne wrote: > On Fri, Sep 4, 2009 at 6:25 AM, wrote: >>> I suggest to add another core PropertyEvaluator that works like the one >>> for toString but doesn't invoke toString() on the reference (but leaves >>> that to IntrospectionHelper if necessary). >>> The ${ref:

Re: How about ${fromRefId:some-reference}?

2009-09-04 Thread Dominique Devienne
On Fri, Sep 4, 2009 at 6:25 AM, wrote: >>I suggest to add another core PropertyEvaluator that works like the one >>for toString but doesn't invoke toString() on the reference (but leaves >>that to IntrospectionHelper if necessary). >> >>The ${ref:} and ${refid:} ideas look prettier but are more li

AW: How about ${fromRefId:some-reference}?

2009-09-04 Thread Jan.Materne
>we have a PropertyEvaluator for ${toString:some-id} that looks up an >object with id "some-id" in the current project and expands to either >null (reference doesn't exist) or the result of calling toString() on >the object. > >With trunk PropertyEvaluators can return non-Strings as values for >pro

How about ${fromRefId:some-reference}?

2009-09-04 Thread Stefan Bodewig
Hi, we have a PropertyEvaluator for ${toString:some-id} that looks up an object with id "some-id" in the current project and expands to either null (reference doesn't exist) or the result of calling toString() on the object. With trunk PropertyEvaluators can return non-Strings as values for prope

Re: PropertyHelper API

2009-09-04 Thread Stefan Bodewig
On 2009-09-01, Matt Benson wrote: > Note that the props antlib does provide a NestedPropertyExpander, so > you're right on track. Thanks, I've modified the documentation to link to it. > The NullReturn thing, IIRC, was added by Peter. Now documented explicitly. Thanks for checking Ste