You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Jason van Zyl <ja...@zenplex.com> on 2002/07/10 22:43:00 UTC
Re: cvs commit:
jakarta-commons-sandbox/jelly/src/java/org/apache/commons/jelly/tags/define
DynamicTag.java
On Wed, 2002-07-10 at 15:57, jvanzyl@apache.org wrote:
> jvanzyl 2002/07/10 12:57:55
>
> Modified: jelly/src/java/org/apache/commons/jelly/tags/define
> DynamicTag.java
> Log:
> o Making the newly created context available in the dynamic tag.
>
> James, if this is evil let me know. But in other jelly scripts I have
> access to the context which is very convenient. In this particular case
> I am trying to access the maven POM inside a dynamic tag lib and I couldn't
> without this change.
Maybe a general setInherit(true) might be better ... Maybe something like
<define:taglib uri="maven">
<define:tag name="foo" inherit="true">
check some stuff
<define:invokeBody/>
</define:tag>
</define:taglib>
I made some custom dynamic tag libs for doing various things but when
doing something like:
<m:foo>
I need access to ${maven.build.dir}
</m:foo>
And I've lost sight of all thing that have been pushed into the context.
--
jvz.
Jason van Zyl
jason@apache.org
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>