+1 here
Is <property> allowed inside <task>, currently?
> -----Original Message-----
> From: Roger Vaughn [mailto:[EMAIL PROTECTED]
> Sent: Sunday, January 14, 2001 10:56 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Property substitutions, Contributed Tasks, & New features
>
>
> Darned if this isn't the best proposal I've yet heard to answer this
> long-running question.
>
> +1
>
>
> Diane Holt wrote:
>
> > --- James Duncan Davidson <[EMAIL PROTECTED]> wrote:
> > > If we go Workspace/Module --
> >
> > Is "Module" defined as the current buildfile?
> >
> > Also, instead of having two separate tags to set a property, couldn't we
> > just (I think something like this might have even been suggested before)
> > add some attributes to <property>:
> > scope="global | module | target"
> > static="yes | no"
> > where:
> > global = workspace-wide (carried into calls to sub-buildfiles)
> > module = current buildfile only (any file "include"d gets
> these as well)
> > target = current target only
> > static = immutable or mutable
> >
> > The buildfile writer decides which to make what, based on the
> logic of how
> > they put the put the build together.
> >
> > Diane
> >
> > =====
> > ([EMAIL PROTECTED])
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
