You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by di...@multitask.com.au on 2002/12/01 00:06:28 UTC
RE: cvs commit: jakarta-turbine-maven/src/plugins-build/cactus plugin.jelly
"Vincent Massol" <vm...@octo.com> wrote on 30/11/2002 10:25:41 PM:
> Hi dIon,
>
> I've been away for some time so I may be missing a few things. Could you
> explain to me why you have made public goals which were private by
> design (at least for the cactus plugin)? Is there some new rule that
> says that all goals must be public? If so, what's the rationale? I did
> not want to expose them as they are subject to changes (not part of the
> plugin GPI - Goal Progamming Interface ;-) ).
AFAIK, they weren't private. They just kept coming up as 'undocumented
goals' when I ran maven -g.
So they were listed at the end of the goals, in the most visible place to
me. I was trying to get the documentation up to scratch, so that they were
all documented.
If you think they need to be marked as Private somehow, lets find a way.
Either:
a) Undocumented goals don't get listed in maven -g,
b) The description has a special 'Private' at the front, or
c) <Insert your suggestion here>
Votes?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
RE: cvs commit: jakarta-turbine-maven/src/plugins-build/cactus plugin.jelly
Posted by di...@multitask.com.au.
Is everyone else happy with this?
I can easily implement it.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
"Vincent Massol" <vm...@octo.com>
01/12/2002 10:14 AM
Please respond to
"Turbine Maven Developers List" <tu...@jakarta.apache.org>
To
"'Turbine Maven Developers List'" <tu...@jakarta.apache.org>
cc
Subject
RE: cvs commit: jakarta-turbine-maven/src/plugins-build/cactus
plugin.jelly
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: 30 November 2002 23:06
> To: Turbine Maven Developers List
> Subject: RE: cvs commit:
jakarta-turbine-maven/src/plugins-build/cactus
> plugin.jelly
>
> "Vincent Massol" <vm...@octo.com> wrote on 30/11/2002 10:25:41 PM:
>
> > Hi dIon,
> >
> > I've been away for some time so I may be missing a few things. Could
you
> > explain to me why you have made public goals which were private by
> > design (at least for the cactus plugin)? Is there some new rule that
> > says that all goals must be public? If so, what's the rationale? I
did
> > not want to expose them as they are subject to changes (not part of
the
> > plugin GPI - Goal Progamming Interface ;-) ).
>
> AFAIK, they weren't private.
They were (there is no other way to signal this ATM). This is true at
least for all the plugins I have written.
> They just kept coming up as 'undocumented
> goals' when I ran maven -g.
yeah, and I had suggested in the past that they don't get listed but
somehow it did not make it...
>
> So they were listed at the end of the goals, in the most visible place
to
> me. I was trying to get the documentation up to scratch, so that they
were
> all documented.
That's a nice goal (pun intended).
>
> If you think they need to be marked as Private somehow, lets find a
way.
> Either:
> a) Undocumented goals don't get listed in maven -g,
+1. I really don't see why they should. That will also force "public"
goals to be documented.
> b) The description has a special 'Private' at the front, or
> c) <Insert your suggestion here>
>
> Votes?
Thanks
-Vincent
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
>
> --
> 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>
--
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:NT00093B36
RE: cvs commit: jakarta-turbine-maven/src/plugins-build/cactus plugin.jelly
Posted by Vincent Massol <vm...@octo.com>.
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: 30 November 2002 23:06
> To: Turbine Maven Developers List
> Subject: RE: cvs commit:
jakarta-turbine-maven/src/plugins-build/cactus
> plugin.jelly
>
> "Vincent Massol" <vm...@octo.com> wrote on 30/11/2002 10:25:41 PM:
>
> > Hi dIon,
> >
> > I've been away for some time so I may be missing a few things. Could
you
> > explain to me why you have made public goals which were private by
> > design (at least for the cactus plugin)? Is there some new rule that
> > says that all goals must be public? If so, what's the rationale? I
did
> > not want to expose them as they are subject to changes (not part of
the
> > plugin GPI - Goal Progamming Interface ;-) ).
>
> AFAIK, they weren't private.
They were (there is no other way to signal this ATM). This is true at
least for all the plugins I have written.
> They just kept coming up as 'undocumented
> goals' when I ran maven -g.
yeah, and I had suggested in the past that they don't get listed but
somehow it did not make it...
>
> So they were listed at the end of the goals, in the most visible place
to
> me. I was trying to get the documentation up to scratch, so that they
were
> all documented.
That's a nice goal (pun intended).
>
> If you think they need to be marked as Private somehow, lets find a
way.
> Either:
> a) Undocumented goals don't get listed in maven -g,
+1. I really don't see why they should. That will also force "public"
goals to be documented.
> b) The description has a special 'Private' at the front, or
> c) <Insert your suggestion here>
>
> Votes?
Thanks
-Vincent
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
>
> --
> 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>