Adding magic properties for targets?

[Stefan Bodewig]

Hi all,

Colm's patch in
 adds two
new magic properties, one for the build's default target and one for
the targets specified on the command line (or via <*ant*>).

IIRC such properties have been suggested many moons ago and rejected,
but now the dev community is a different one and maybe we do see some
things differently today.  I know that I do, i.e. I'd probably add
them today.

Before I start to discuss gritty details of a really trivial patch,
let's have a quick poll so we know whether such a feature would be
acceptable.  If anybody out there would reject either property, could
you please raise your hand?

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: Adding magic properties for targets?

[Jan.Materne]

> Colm's patch in
>  adds two
> new magic properties, one for the build's default target and one for
> the targets specified on the command line (or via <*ant*>).
> 
> IIRC such properties have been suggested many moons ago and rejected,
> but now the dev community is a different one and maybe we do see some
> things differently today.  I know that I do, i.e. I'd probably add
> them today.
> 
> Before I start to discuss gritty details of a really trivial patch,
> let's have a quick poll so we know whether such a feature would be
> acceptable.  If anybody out there would reject either property, could
> you please raise your hand?


${defaultTarget}:
   +1 : I am not sure if there is need, but I dont see any reason of
hiding that information
as it currently available via project instance.

${calledTargets}:
   +1 : Also, we dont have to hide anything. The value should be a list
of targets 
as specified while invocation without any dependency-resolution.

These properties should be set while parsing/project-initialization, so
IDEs/programs,
which dont use the Launcher, have these properties too.


Jan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Adding magic properties for targets?

[Dominique Devienne]

I'd add that those properties, if made available, should probably be
prefixed with ant., to make it clear they are "built-in". Perhaps:

ant.default-target
ant.targets-invoked

I'm +0 on adding these "static" properties.

Since we're at it, we may also want to expose ant.current-target and
ant.invoked-target properties, but these are "dynamic" since changing
during the course of the build, so more problematic given the property
immutability rules. Exposing them via a PropertyHelper to made it
clear they are dynamic perhaps? ${dynamic:ant.current-target}...

--DD

On Fri, May 30, 2008 at 4:21 AM,  <[EMAIL PROTECTED]> wrote:
>> Colm's patch in
>>  adds two
>> new magic properties, one for the build's default target and one for
>> the targets specified on the command line (or via <*ant*>).
>>
>> IIRC such properties have been suggested many moons ago and rejected,
>> but now the dev community is a different one and maybe we do see some
>> things differently today.  I know that I do, i.e. I'd probably add
>> them today.
>>
>> Before I start to discuss gritty details of a really trivial patch,
>> let's have a quick poll so we know whether such a feature would be
>> acceptable.  If anybody out there would reject either property, could
>> you please raise your hand?
>
>
> ${defaultTarget}:
>   +1 : I am not sure if there is need, but I dont see any reason of
> hiding that information
>as it currently available via project instance.
>
> ${calledTargets}:
>   +1 : Also, we dont have to hide anything. The value should be a list
> of targets
>as specified while invocation without any dependency-resolution.
>
> These properties should be set while parsing/project-initialization, so
> IDEs/programs,
> which dont use the Launcher, have these properties too.
>
>
> Jan
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Adding magic properties for targets?

[Kevin Jackson]

Hi,

> Colm's patch in
>  adds two
> new magic properties, one for the build's default target and one for
> the targets specified on the command line (or via <*ant*>).
>
> IIRC such properties have been suggested many moons ago and rejected,
> but now the dev community is a different one and maybe we do see some
> things differently today.  I know that I do, i.e. I'd probably add
> them today.
>
> Before I start to discuss gritty details of a really trivial patch,
> let's have a quick poll so we know whether such a feature would be
> acceptable.  If anybody out there would reject either property, could
> you please raise your hand?

I probably wasn't around when these properties were first discussed,
but I don't see any harm in allowing access to what are essentially
static values.
+0

Kev

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]