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/01/12 00:00:11 UTC
Re: cvs commit: jakarta-turbine-maven/src/plugins-build/site
plugin.properties
On Sat, 2003-01-11 at 17:07, dion@apache.org wrote:
> dion 2003/01/11 14:07:22
>
> Modified: src/plugins-build/site plugin.properties
> Log:
> Temporarily adding property until inter-plugin property issue can be resolved
>
> Revision Changes Path
> 1.3 +7 -0 jakarta-turbine-maven/src/plugins-build/site/plugin.properties
>
> Index: plugin.properties
> ===================================================================
> RCS file: /home/cvs/jakarta-turbine-maven/src/plugins-build/site/plugin.properties,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -u -r1.2 -r1.3
> --- plugin.properties 26 Oct 2002 15:52:33 -0000 1.2
> +++ plugin.properties 11 Jan 2003 22:07:22 -0000 1.3
> @@ -20,3 +20,10 @@
> maven.site.deploy.method=ssh
>
> maven.username=USERNAME_NOT_SET
> +
> +#
> +# FIXME: This is a copy of maven.docs.dest, as there is a dependency
> +# issue where plugins dont get access to other plugins properties
> +# from the context
> +#
> +maven.docs.dest = ${maven.build.dir}/docs
> \ No newline at end of file
They are not directly accessible but they are accessible via something
like this:
${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.gen.docs')}
Which shows some weirdness in the plugin naming which I was thinking
about and eventually forgot to mention the above usage. The xdoc plugin
and the sea plugin use this to get access to plugin properties.
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.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
Re: cvs commit:
jakarta-turbine-maven/src/plugins-build/site plugin.properties
Posted by Jason van Zyl <ja...@zenplex.com>.
On Sat, 2003-01-11 at 18:40, dion@multitask.com.au wrote:
> So is this the recommended way from now on?
Yes, if we can simplify we can do so in one sweep. But I am also trying
to hide the use of this in dyna tags. If you look in the xdoc plugin and
the <doc:jsl/> in particular you'll see what I'm trying to do. I'm
trying to expose the functionality of a plugin via dyna tags so people
can use simple parameters and hide the gory details of inter-plugin
whackiness if possible. I think in most cases this can be done. Sorry
for the late explanation.
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
> Jason van Zyl <ja...@zenplex.com> wrote on 12/01/2003 10:00:11 AM:
>
> > On Sat, 2003-01-11 at 17:07, dion@apache.org wrote:
> > > dion 2003/01/11 14:07:22
> > >
> > > Modified: src/plugins-build/site plugin.properties
> > > Log:
> > > Temporarily adding property until inter-plugin property issue
> > can be resolved
> > >
> > > Revision Changes Path
> > > 1.3 +7 -0 jakarta-turbine-maven/src/plugins-
> > build/site/plugin.properties
> > >
> > > Index: plugin.properties
> > > ===================================================================
> > > RCS file: /home/cvs/jakarta-turbine-maven/src/plugins-
> > build/site/plugin.properties,v
> > > retrieving revision 1.2
> > > retrieving revision 1.3
> > > diff -u -r1.2 -r1.3
> > > --- plugin.properties 26 Oct 2002 15:52:33 -0000 1.2
> > > +++ plugin.properties 11 Jan 2003 22:07:22 -0000 1.3
> > > @@ -20,3 +20,10 @@
> > > maven.site.deploy.method=ssh
> > >
> > > maven.username=USERNAME_NOT_SET
> > > +
> > > +#
> > > +# FIXME: This is a copy of maven.docs.dest, as there is a
> dependency
> > > +# issue where plugins dont get access to other plugins
> properties
> > > +# from the context
> > > +#
> > > +maven.docs.dest = ${maven.build.dir}/docs
> > > \ No newline at end of file
> >
> > They are not directly accessible but they are accessible via something
> > like this:
> >
> >
> ${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.gen.docs')}
> >
> > Which shows some weirdness in the plugin naming which I was thinking
> > about and eventually forgot to mention the above usage. The xdoc plugin
> > and the sea plugin use this to get access to plugin properties.
> >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <mailto:turbine-maven-dev-
> > unsubscribe@jakarta.apache.org>
> > > For additional commands, e-mail: <mailto:turbine-maven-dev-
> > help@jakarta.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: <mailto:turbine-maven-dev-
> > unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: <mailto:turbine-maven-dev-
> > help@jakarta.apache.org>
> >
>
> > ForwardSourceID:NT000A1EB6
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.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
Re: cvs commit: jakarta-turbine-maven/src/plugins-build/site plugin.properties
Posted by di...@multitask.com.au.
So is this the recommended way from now on?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Jason van Zyl <ja...@zenplex.com> wrote on 12/01/2003 10:00:11 AM:
> On Sat, 2003-01-11 at 17:07, dion@apache.org wrote:
> > dion 2003/01/11 14:07:22
> >
> > Modified: src/plugins-build/site plugin.properties
> > Log:
> > Temporarily adding property until inter-plugin property issue
> can be resolved
> >
> > Revision Changes Path
> > 1.3 +7 -0 jakarta-turbine-maven/src/plugins-
> build/site/plugin.properties
> >
> > Index: plugin.properties
> > ===================================================================
> > RCS file: /home/cvs/jakarta-turbine-maven/src/plugins-
> build/site/plugin.properties,v
> > retrieving revision 1.2
> > retrieving revision 1.3
> > diff -u -r1.2 -r1.3
> > --- plugin.properties 26 Oct 2002 15:52:33 -0000 1.2
> > +++ plugin.properties 11 Jan 2003 22:07:22 -0000 1.3
> > @@ -20,3 +20,10 @@
> > maven.site.deploy.method=ssh
> >
> > maven.username=USERNAME_NOT_SET
> > +
> > +#
> > +# FIXME: This is a copy of maven.docs.dest, as there is a
dependency
> > +# issue where plugins dont get access to other plugins
properties
> > +# from the context
> > +#
> > +maven.docs.dest = ${maven.build.dir}/docs
> > \ No newline at end of file
>
> They are not directly accessible but they are accessible via something
> like this:
>
>
${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.gen.docs')}
>
> Which shows some weirdness in the plugin naming which I was thinking
> about and eventually forgot to mention the above usage. The xdoc plugin
> and the sea plugin use this to get access to plugin properties.
>
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <mailto:turbine-maven-dev-
> unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: <mailto:turbine-maven-dev-
> help@jakarta.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: <mailto:turbine-maven-dev-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:turbine-maven-dev-
> help@jakarta.apache.org>
>
> ForwardSourceID:NT000A1EB6