urden ere at work.
>
> Jose Alberto
>
> > -Original Message-
> > From: peter reilly [mailto:[EMAIL PROTECTED]
> > Sent: 20 October 2003 16:54
> > To: Ant Developers List
> > Subject: Re: Macrodef and parallel in a recursive situation
> >
> &
kind of burden ere at work.
Jose Alberto
> -Original Message-
> From: peter reilly [mailto:[EMAIL PROTECTED]
> Sent: 20 October 2003 16:54
> To: Ant Developers List
> Subject: Re: Macrodef and parallel in a recursive situation
>
>
> This is basicly what the loc
Gotcha--I missed that the first time around. If you
want to restrict the scope of a property set by a
task, you essentially reserve that property in the
local context, then invoke the task. This should work
although I like my way better... ;)
I think it is okay to force the user to explicitly
se
This is basicly what the local implementation
does.
The only problem is for ant/antcall, a new project
is created and the local properties would need
to be copied to this, keeping in mind all the
rules about user/normal/inherited and nested param
elements.
Peter
On Monday 20 October 2003 16:16, M
> handled some other way? What about a Scope
> TaskContainer subclass that would push an element
I meant "implementation."
-Matt
__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
Jose makes a good point about tasks that set
properties. Without having delved into the
PropertyHelper* classes, could local properties be
handled some other way? What about a Scope
TaskContainer subclass that would push an element onto
a stack. Then any property queries would descend into
the s
> From: peter reilly [mailto:[EMAIL PROTECTED]
>
> On Monday 20 October 2003 13:25, Jose Alberto Fernandez wrote:
> >
> > So what do I get on the ant/antcall/subant side of things?
> > Do I get the original global value? Or nothing?
>
> The original global value.
>
I think I have misgivings ab
On Monday 20 October 2003 13:38, Christopher Lenz wrote:
> Hi Peter,
>
> this looks really cool, but I'd suggest adding an attribute like
> scope="local|global" to the task instead of adding a completely
> new task.
I had thought of that but shyed away for the moment as
the property task allows m
> From: Christopher Lenz [mailto:[EMAIL PROTECTED]
>
> Hi Peter,
>
> this looks really cool, but I'd suggest adding an attribute like
> scope="local|global" to the task instead of adding
> a completely
> new task.
>
I disagree here. The issue is not by itself. This local
properties need t
On Monday 20 October 2003 13:25, Jose Alberto Fernandez wrote:
> > From: peter reilly [mailto:[EMAIL PROTECTED]
> >
> > On Monday 20 October 2003 11:43, Jose Alberto Fernandez wrote:
> > > Peter,
> > >
> > > sounds great. How does your implementation using threadLocal works
> > > when going across
Hi Peter,
this looks really cool, but I'd suggest adding an attribute like
scope="local|global" to the task instead of adding a completely
new task.
-chris
peter reilly wrote:
I have written the code to support local properties.
While I was doing this, I realized that the attributes
of a macrod
> From: peter reilly [mailto:[EMAIL PROTECTED]
>
> On Monday 20 October 2003 11:43, Jose Alberto Fernandez wrote:
> > Peter,
> >
> > sounds great. How does your implementation using threadLocal works
> > when going across or ? Just curious.
>
> The local properties do not cross to the ant/antc
y are "local", they do
not need to.
Peter
>
> Jose Alberto
>
> > -Original Message-
> > From: peter reilly [mailto:[EMAIL PROTECTED]
> > Sent: 20 October 2003 09:59
> > To: Ant Developers List
> > Subject: Re: Macrodef and parallel in a recur
ef and parallel in a recursive situation
>
>
> I have written the code to support local properties.
> While I was doing this, I realized that the attributes
> of a macrodef could/should be local properties as well,
> removing some of the issues seen last week (use of attribute
I have written the code to support local properties.
While I was doing this, I realized that the attributes
of a macrodef could/should be local properties as well,
removing some of the issues seen last week (use of
attribute in a bsf script and support of parallel/recursive).
The following shows i
> From: peter reilly [mailto:[EMAIL PROTECTED]
>
> I think that we may need a thread local variable to
> handle parallel.
>
> This would mean some deep messing with the Property handling.
>
I do not see how thread locals would help here. I guess the
question is whether tasks in parallel should
; >
> > >
> > >
> > > ...
> > >
> > >
> > > Then when you call "recursive" such as this: > > current="0" method="blah"/> it won't die that you did not pass
> > > "newcurrent".
>
attribute name could be something else, or
> > scope="static" and a list of others that could be used.
> >
> > -- Larry
> >
> > > -Original Message-
> > > From: peter reilly [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, October 17
ass
> "newcurrent".
>
> the "staticscope" attribute name could be something else, or scope="static"
> and a list of others that could be used.
>
> -- Larry
>
> > -Original Message-----
> > From: peter reilly [mailto:[EMAIL PROTECTED]
newcurrent".
the "staticscope" attribute name could be something else, or scope="static"
and a list of others that could be used.
-- Larry
> -Original Message-
> From: peter reilly [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 17, 2003 12:43 AM
> To: Ant
: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 17, 2003 4:42 AM
> To: Ant Developers List
> Subject: RE: Macrodef and parallel in a recursive situation
>
>
> For a long time I have thought on adding local contet to ANT.
> In principle it would be something like:
>
>
>
>
> ...
>
>
For a long time I have thought on adding local contet to ANT.
In principle it would be something like:
...
> hod"/>
> >
> >
> >
> >
> >
> >
> >
> >> datatype = "int"
> > operand1 = "${curren
> I have run into a possible bug when working with macrodef and parallel in a
> recursive situation.
>
> The following build file snip example exhibits this: (This requires the
> ant-contrib task, and fr
I have run into a possible bug when working with macrodef and parallel in a
recursive situation.
The following build file snip example exhibits this: (This requires the
ant-contrib task, and from Antelope, soon to be ant-contrib
24 matches
Mail list logo
