You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@zenplex.com> on 2003/06/29 21:59:52 UTC
Use of Jelly scopes in plugins
Howdy,
The last hiccup I've run into is the jelly scope test in the touchstone
build. I looked at it and wondered why this is even needed so I looked
through the plugins and found all sorts of references to setting
variables with scopes. The following plugins have this attribute:
clover
javadoc
junit-report
plugin
repository
For anyone who added the use of scopes what exactly is the purpose? I'm
trying to clarify where things are defined and the exact behaviour of
contexts. Are these uses for cross-plugin communication? I would really
like to eliminate the use of scopes all together.
--
jvz.
Jason van Zyl
jason@zenplex.com
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Use of Jelly scopes in plugins
Posted by di...@multitask.com.au.
Jason van Zyl <ja...@zenplex.com> wrote on 30/06/2003 11:48:55 AM:
> On Sun, 2003-06-29 at 19:01, dion@multitask.com.au wrote:
> > With the repository plugin, the use of the parent scope is to 'return'
a
> > variable from a tag in a plugin. The use of the system scope is to
access
> > system properties.
>
> The system properties have always been available so that's not a
> problem.
>
> So in the repository plugin it's used as a means to return a value.
> You're using it like a method, sort of?
Sort of. One tag parses a file and makes it available in the caller's
context, e.g.
<repository:parseAudit var="audit"/>
The caller is the parent scope to the tag.
> > With the plugin plugin, it's used to read a property file into it's
own
> > scope and pass them as a single map back to the parent.
>
> What's the parent in this case?
A goal in the same plugin.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Re: Use of Jelly scopes in plugins
Posted by Jason van Zyl <ja...@zenplex.com>.
On Sun, 2003-06-29 at 19:01, dion@multitask.com.au wrote:
> With the repository plugin, the use of the parent scope is to 'return' a
> variable from a tag in a plugin. The use of the system scope is to access
> system properties.
The system properties have always been available so that's not a
problem.
So in the repository plugin it's used as a means to return a value.
You're using it like a method, sort of?
> With the plugin plugin, it's used to read a property file into it's own
> scope and pass them as a single map back to the parent.
What's the parent in this case?
> These, or something to replace them are necessary.
Yup, no problem.
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
> Work: http://www.multitask.com.au
>
>
> Jason van Zyl <ja...@zenplex.com> wrote on 30/06/2003 05:59:52 AM:
>
> > Howdy,
> >
> > The last hiccup I've run into is the jelly scope test in the touchstone
> > build. I looked at it and wondered why this is even needed so I looked
> > through the plugins and found all sorts of references to setting
> > variables with scopes. The following plugins have this attribute:
> >
> > clover
> > javadoc
> > junit-report
> > plugin
> > repository
> >
> > For anyone who added the use of scopes what exactly is the purpose? I'm
> > trying to clarify where things are defined and the exact behaviour of
> > contexts. Are these uses for cross-plugin communication? I would really
> > like to eliminate the use of scopes all together.
> >
> > --
> > jvz.
> >
> > Jason van Zyl
> > jason@zenplex.com
> > 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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
--
jvz.
Jason van Zyl
jason@zenplex.com
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Use of Jelly scopes in plugins
Posted by di...@multitask.com.au.
With the repository plugin, the use of the parent scope is to 'return' a
variable from a tag in a plugin. The use of the system scope is to access
system properties.
With the plugin plugin, it's used to read a property file into it's own
scope and pass them as a single map back to the parent.
These, or something to replace them are necessary.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Jason van Zyl <ja...@zenplex.com> wrote on 30/06/2003 05:59:52 AM:
> Howdy,
>
> The last hiccup I've run into is the jelly scope test in the touchstone
> build. I looked at it and wondered why this is even needed so I looked
> through the plugins and found all sorts of references to setting
> variables with scopes. The following plugins have this attribute:
>
> clover
> javadoc
> junit-report
> plugin
> repository
>
> For anyone who added the use of scopes what exactly is the purpose? I'm
> trying to clarify where things are defined and the exact behaviour of
> contexts. Are these uses for cross-plugin communication? I would really
> like to eliminate the use of scopes all together.
>
> --
> jvz.
>
> Jason van Zyl
> jason@zenplex.com
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>