On 2010-06-21, Dominique Devienne wrote:
> On Mon, Jun 21, 2010 at 2:18 AM, Stefan Bodewig wrote:
>> loadproperties already can.
>> [...]
>>
>>
>>
>>
>>
>> you get
>> foo.y=${x}
> Well likely applies on the property file "text", not its
> "infoset", so will prefix comments and contin
On 06/19/2010 02:38 PM, Bruce Atherton wrote:
1. Should the following commercial tasks be dropped from being
distributed with the Ant release?
+1 for all.
2. Should the commercial tasks that are voted for dropping from Ant core
above be established in their own Antlibs in the sandbox?
[ ] +1
On Mon, Jun 21, 2010 at 2:18 AM, Stefan Bodewig wrote:
> loadproperties already can.
> [...]
>
>
>
>
>
>
> you get
> foo.y=${x}
Well likely applies on the property file "text", not its
"infoset", so will prefix comments and continuation lines as well,
leading to an possibly incorrect f
On 2010-06-21, Danny Yates wrote:
> Anything I can do to assist?
Wait and answer questions/concerns as they arrise (if they arrise).
Nag and become annoying if you feel it takes too long ;-)
Stefan
-
To unsubscribe, e-mail: de
Thanks Stefan.
Anything I can do to assist?
Cheers,
Danny.
On 21 June 2010 07:59, Stefan Bodewig wrote:
> On 2010-06-19, Danny Yates wrote:
>
> > I've made some changes to add an "extension-point-missing" attribute
> which
> > takes values:
>
> >- "error" - the current behaviour (and defa
On 19 June 2010 20:38, Bruce Atherton wrote:
>
> 1. Should the following commercial tasks be dropped from being distributed
> with the Ant release?
>
> [ ] Continuous/Synergy tasks: CCMCheckin, CCMCheckout, CCMCheckinTask,
> CCMReconfigure, CCMCreateTask
> [ ] Clearcase tasks: CCCheckin, CCCh
On 2010-06-19, Bruce Atherton wrote:
> 1. Should the following commercial tasks be dropped from being
> distributed with the Ant release?
> [ ] Continuous/Synergy tasks: CCMCheckin, CCMCheckout,
> CCMCheckinTask, CCMReconfigure, CCMCreateTask
> [ ] Clearcase tasks: CCCheckin, CCCheckou
On 2010-06-18, Bruce Atherton wrote:
> I would argue for the opposite (although I don't know how practical it
> is). Would it be possible for loadproperties to not only prefix the
> properties that are defined, but also the properties to be expanded?
> So "y=${x}" becomes "foo.y=${foo.x}"?
loadpr
On 2010-06-18, Dominique Devienne wrote:
> On Fri, Jun 18, 2010 at 2:47 AM, Stefan Bodewig wrote:
>> On 06/17/2010 11:10 AM, Stefan Bodewig wrote:
>> Assume
>> x=x
>> y=${x}
>> and that there is no property x defined prior to
>>
>> then ${y} will be "x". Using
>>
>> ${foo.y} in Ant
On 2010-06-19, Danny Yates wrote:
> I've made some changes to add an "extension-point-missing" attribute which
> takes values:
>- "error" - the current behaviour (and default if the attribute is
>missing)
>- "warn" - log a warning and ignore (see next)
>- "ignore" - don't stop or
10 matches
Mail list logo