You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2006/06/28 18:10:33 UTC
generated plugin documentation: opinions?
Hi,
Edwin has come up with this:
http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
Any feedback before I apply it?
- Brett
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Edwin Punzalan <ep...@exist.com>.
There's a guide for configuring plugins and it mentions lists and maps...
http://maven.apache.org/guides/mini/guide-configuring-plugins.html
Brett Porter wrote:
> On 29/06/2006 4:14 PM, Wendy Smoak wrote:
>> On 6/28/06, Brett Porter <br...@apache.org> wrote:
>>
>>> Sorry, but I don't really understand what you are asking here.
>>
>> A plugin attribute of 'filters' that is of type 'List' did not suggest
>> to me that I ought to type <filters><filter>. If anything, I would
>> have thought it meant a comma-delimited list on the comand line:
>> -Dfilters=filterOne,filterTwo
>>
>> Clearly I've missed some basic information, and I'm wondering if it's
>> somewhere in the documentation, or if this might be one of those
>> things you "just know" if you've been working with, say, Plexus (which
>> I haven't.)
>>
>> (Now, I've seen enough example plugin configurations to figure it out,
>> but the fact is that just reading the plugin attributes page for an m2
>> plugin wasn't enough. With Maven 1, it seemed like the corresponding
>> page of plugin 'properties' was all I needed.)
>>
>
> Yeah, it never had lists :)
>
> I think this would be a good thing for a cheat sheet like Mike was
> talking about. So a "guide to configuring plugins" of some sort.
>
> In the long run, I'd like the lists/maps to be typed (you can do this
> with arrays now, but could do it for all using generics), which would
> make this a little clearer in the docs too.
>
> Cheers,
> Brett
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Brett Porter <br...@apache.org>.
On 29/06/2006 4:14 PM, Wendy Smoak wrote:
> On 6/28/06, Brett Porter <br...@apache.org> wrote:
>
>> Sorry, but I don't really understand what you are asking here.
>
> A plugin attribute of 'filters' that is of type 'List' did not suggest
> to me that I ought to type <filters><filter>. If anything, I would
> have thought it meant a comma-delimited list on the comand line:
> -Dfilters=filterOne,filterTwo
>
> Clearly I've missed some basic information, and I'm wondering if it's
> somewhere in the documentation, or if this might be one of those
> things you "just know" if you've been working with, say, Plexus (which
> I haven't.)
>
> (Now, I've seen enough example plugin configurations to figure it out,
> but the fact is that just reading the plugin attributes page for an m2
> plugin wasn't enough. With Maven 1, it seemed like the corresponding
> page of plugin 'properties' was all I needed.)
>
Yeah, it never had lists :)
I think this would be a good thing for a cheat sheet like Mike was
talking about. So a "guide to configuring plugins" of some sort.
In the long run, I'd like the lists/maps to be typed (you can do this
with arrays now, but could do it for all using generics), which would
make this a little clearer in the docs too.
Cheers,
Brett
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Wendy Smoak <ws...@gmail.com>.
On 6/28/06, Brett Porter <br...@apache.org> wrote:
> Sorry, but I don't really understand what you are asking here.
A plugin attribute of 'filters' that is of type 'List' did not suggest
to me that I ought to type <filters><filter>. If anything, I would
have thought it meant a comma-delimited list on the comand line:
-Dfilters=filterOne,filterTwo
Clearly I've missed some basic information, and I'm wondering if it's
somewhere in the documentation, or if this might be one of those
things you "just know" if you've been working with, say, Plexus (which
I haven't.)
(Now, I've seen enough example plugin configurations to figure it out,
but the fact is that just reading the plugin attributes page for an m2
plugin wasn't enough. With Maven 1, it seemed like the corresponding
page of plugin 'properties' was all I needed.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Brett Porter <br...@apache.org>.
Wendy,
Sorry, but I don't really understand what you are asking here. And
thanks for correcting my embarrassing typo :)
- Brett
On 29/06/2006 1:39 PM, Wendy Smoak wrote:
> On 6/28/06, Brett Porter <br...@apache.org> wrote:
>
>> [Isn't it] helpful, like the default value, to know what the constraints
>> are for what you enter? And I'd argue lists are very useful as they
>> indicate how you have to specify it (<filters><filter> vs just <filter>).
>
> (Aside: Now, it is. Apparently, I missed that page of the manual. :)
> Where should I have learned this? Searching for 'maven plugin
> attribute types' isn't too useful.)
>
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Wendy Smoak <ws...@gmail.com>.
On 6/28/06, Brett Porter <br...@apache.org> wrote:
> [Isn't it] helpful, like the default value, to know what the constraints
> are for what you enter? And I'd argue lists are very useful as they
> indicate how you have to specify it (<filters><filter> vs just <filter>).
(Aside: Now, it is. Apparently, I missed that page of the manual. :)
Where should I have learned this? Searching for 'maven plugin
attribute types' isn't too useful.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Brett Porter <br...@apache.org>.
On 29/06/2006 3:52 AM, Wendy Smoak wrote:
> On 6/28/06, Brett Porter <br...@apache.org> wrote:
>
>> Edwin has come up with this:
>> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>>
>> Any feedback before I apply it?
>
> Thanks, Edwin! I'd probably drop 'type' from the table at the top,
> and just have attribute name and description.
>
> The 'type' isn't very useful to me... when I'm attempting to configure
> a plugin, what does it mean that 'filters' is of type List?
Is'n tit helpful, like the default value, to know what the constraints
are for what you enter? And I'd argue lists are very useful as they
indicate how you have to specify it (<filters><filter> vs just <filter>).
>
> I assume 'No description' is no longer allowed under the new guidelines. :)
>
Right :)
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Wendy Smoak <ws...@gmail.com>.
On 6/28/06, Brett Porter <br...@apache.org> wrote:
> Edwin has come up with this:
> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>
> Any feedback before I apply it?
Thanks, Edwin! I'd probably drop 'type' from the table at the top,
and just have attribute name and description.
The 'type' isn't very useful to me... when I'm attempting to configure
a plugin, what does it mean that 'filters' is of type List?
I assume 'No description' is no longer allowed under the new guidelines. :)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Brett Porter <br...@apache.org>.
It's the wrapping we're trying to avoid:
http://maven.apache.org/plugins/maven-site-plugin/stage-deploy-mojo.html
The default will always be pulled out in the list of the verbose
description, I tink it was just suggested that it be in the description
in the top table (always at the end).
- Brett
On 29/06/2006 1:22 PM, Jeff Jensen wrote:
> I think default values should be in their own column so it is easier to
> see/read/find. I find other plugins that have done this much nicer to use.
> I very much dislike pages that have buried the defaults somewhere in the
> description (front, middle, end - doesn't matter). I also found that when
> buried in the description, some are skipped - e.g. too easy to miss, or
> didn't think to write it.
>
> A "valid values" column is also nice for listing the domain of them.
>
> I'll take the width. The browser wraps the text in the columns anyway...
>
>
> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: Wednesday, June 28, 2006 10:06 PM
> To: Maven Developers List
> Subject: Re: generated plugin documentation: opinions?
>
> I agree with copying the default value into the end of the description.
> The reason it isn't in the table as a column is that it is too wide,
> usually.
>
> I would leave the expression as just the expression in the latter part as it
> is now. We've already agreed this is unclear and will deprecate it in 2.1 in
> favour of:
>
> - default-value="..." (always the default, can contain expressions)
> - propertyKey="maven.test.skip" (instead of expression ${maven.test.skip},
> for allowing properties to configure it from the pom, settings and command
> line. Perhaps needs a different name).
>
> I guess we could hack it such that expressions that aren't project.* or
> settings.* are treated that way in the document, but let's think some more
> about that.
>
> As for the other suggests - I also agree we should have a little summary at
> the top that shows the mojo level metadata (@phase, @goal, @execute,
> @requiresDependencyResolution).
>
> I also agree we should link to the Javadoc of complex types. However, this
> is non-trivial, so let's enter it as a new JIRA issue for now.
>
> Cheers,
> Brett
>
> On 29/06/2006 12:53 PM, Edwin Punzalan wrote:
>> +1 for moving the default value. A lot of the other comments want the
>> default value at the top of the page. Showing the default value in a
>> sentence is nice too.
>>
>> It just somehow becomes complicated because expressions functions
>> somewhat like a default value, too. Any suggestions on how to handle
> that?
>>
>> Mark Hobson wrote:
>>> Definitely a big improvement :)
>>>
>>> I agree that it'd be nice to see the default value for optional
>>> parameters in the table. Perhaps append it to the description, e.g.
>>>
>>> appendAssemblyId boolean Set to false to exclude the
>>> assembly id
>>> from the assembly final name. (Default value is true)
>>>
>>> Also it'd be nice at least to link complex object types to their
>>> javadoc, e.g. MavenArchiveConfiguration in maven-jar-plugin. An
>>> example XML block from introspecting the bean would be even better ;)
>>>
>>> Cheers,
>>>
>>> Mark
>>>
>>> On 28/06/06, Brett Porter <br...@apache.org> wrote:
>>>> Hi,
>>>>
>>>> Edwin has come up with this:
>>>> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>>>>
>>>> Any feedback before I apply it?
>>>>
>>>> - Brett
>>>>
>>>> --
>>>> Brett Porter <br...@apache.org>
>>>> Apache Maven - http://maven.apache.org/ Better Builds with Maven -
>>>> http://library.mergere.com/
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>>> additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> additional commands, e-mail: dev-help@maven.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> --
> Brett Porter <br...@apache.org>
> Apache Maven - http://maven.apache.org/
> Better Builds with Maven - http://library.mergere.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
> commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: generated plugin documentation: opinions?
Posted by Jeff Jensen <je...@upstairstechnology.com>.
I think default values should be in their own column so it is easier to
see/read/find. I find other plugins that have done this much nicer to use.
I very much dislike pages that have buried the defaults somewhere in the
description (front, middle, end - doesn't matter). I also found that when
buried in the description, some are skipped - e.g. too easy to miss, or
didn't think to write it.
A "valid values" column is also nice for listing the domain of them.
I'll take the width. The browser wraps the text in the columns anyway...
-----Original Message-----
From: Brett Porter [mailto:brett@apache.org]
Sent: Wednesday, June 28, 2006 10:06 PM
To: Maven Developers List
Subject: Re: generated plugin documentation: opinions?
I agree with copying the default value into the end of the description.
The reason it isn't in the table as a column is that it is too wide,
usually.
I would leave the expression as just the expression in the latter part as it
is now. We've already agreed this is unclear and will deprecate it in 2.1 in
favour of:
- default-value="..." (always the default, can contain expressions)
- propertyKey="maven.test.skip" (instead of expression ${maven.test.skip},
for allowing properties to configure it from the pom, settings and command
line. Perhaps needs a different name).
I guess we could hack it such that expressions that aren't project.* or
settings.* are treated that way in the document, but let's think some more
about that.
As for the other suggests - I also agree we should have a little summary at
the top that shows the mojo level metadata (@phase, @goal, @execute,
@requiresDependencyResolution).
I also agree we should link to the Javadoc of complex types. However, this
is non-trivial, so let's enter it as a new JIRA issue for now.
Cheers,
Brett
On 29/06/2006 12:53 PM, Edwin Punzalan wrote:
>
> +1 for moving the default value. A lot of the other comments want the
> default value at the top of the page. Showing the default value in a
> sentence is nice too.
>
> It just somehow becomes complicated because expressions functions
> somewhat like a default value, too. Any suggestions on how to handle
that?
>
>
> Mark Hobson wrote:
>> Definitely a big improvement :)
>>
>> I agree that it'd be nice to see the default value for optional
>> parameters in the table. Perhaps append it to the description, e.g.
>>
>> appendAssemblyId boolean Set to false to exclude the
>> assembly id
>> from the assembly final name. (Default value is true)
>>
>> Also it'd be nice at least to link complex object types to their
>> javadoc, e.g. MavenArchiveConfiguration in maven-jar-plugin. An
>> example XML block from introspecting the bean would be even better ;)
>>
>> Cheers,
>>
>> Mark
>>
>> On 28/06/06, Brett Porter <br...@apache.org> wrote:
>>> Hi,
>>>
>>> Edwin has come up with this:
>>> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>>>
>>> Any feedback before I apply it?
>>>
>>> - Brett
>>>
>>> --
>>> Brett Porter <br...@apache.org>
>>> Apache Maven - http://maven.apache.org/ Better Builds with Maven -
>>> http://library.mergere.com/
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Brett Porter <br...@apache.org>.
I agree with copying the default value into the end of the description.
The reason it isn't in the table as a column is that it is too wide,
usually.
I would leave the expression as just the expression in the latter part
as it is now. We've already agreed this is unclear and will deprecate it
in 2.1 in favour of:
- default-value="..." (always the default, can contain expressions)
- propertyKey="maven.test.skip" (instead of expression
${maven.test.skip}, for allowing properties to configure it from the
pom, settings and command line. Perhaps needs a different name).
I guess we could hack it such that expressions that aren't project.* or
settings.* are treated that way in the document, but let's think some
more about that.
As for the other suggests - I also agree we should have a little summary
at the top that shows the mojo level metadata (@phase, @goal, @execute,
@requiresDependencyResolution).
I also agree we should link to the Javadoc of complex types. However,
this is non-trivial, so let's enter it as a new JIRA issue for now.
Cheers,
Brett
On 29/06/2006 12:53 PM, Edwin Punzalan wrote:
>
> +1 for moving the default value. A lot of the other comments want the
> default value at the top of the page. Showing the default value in a
> sentence is nice too.
>
> It just somehow becomes complicated because expressions functions
> somewhat like a default value, too. Any suggestions on how to handle that?
>
>
> Mark Hobson wrote:
>> Definitely a big improvement :)
>>
>> I agree that it'd be nice to see the default value for optional
>> parameters in the table. Perhaps append it to the description, e.g.
>>
>> appendAssemblyId boolean Set to false to exclude the
>> assembly id
>> from the assembly final name. (Default value is true)
>>
>> Also it'd be nice at least to link complex object types to their
>> javadoc, e.g. MavenArchiveConfiguration in maven-jar-plugin. An
>> example XML block from introspecting the bean would be even better ;)
>>
>> Cheers,
>>
>> Mark
>>
>> On 28/06/06, Brett Porter <br...@apache.org> wrote:
>>> Hi,
>>>
>>> Edwin has come up with this:
>>> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>>>
>>> Any feedback before I apply it?
>>>
>>> - Brett
>>>
>>> --
>>> Brett Porter <br...@apache.org>
>>> Apache Maven - http://maven.apache.org/
>>> Better Builds with Maven - http://library.mergere.com/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Edwin Punzalan <ep...@exist.com>.
+1 for moving the default value. A lot of the other comments want the
default value at the top of the page. Showing the default value in a
sentence is nice too.
It just somehow becomes complicated because expressions functions
somewhat like a default value, too. Any suggestions on how to handle that?
Mark Hobson wrote:
> Definitely a big improvement :)
>
> I agree that it'd be nice to see the default value for optional
> parameters in the table. Perhaps append it to the description, e.g.
>
> appendAssemblyId boolean Set to false to exclude the
> assembly id
> from the assembly final name. (Default value is true)
>
> Also it'd be nice at least to link complex object types to their
> javadoc, e.g. MavenArchiveConfiguration in maven-jar-plugin. An
> example XML block from introspecting the bean would be even better ;)
>
> Cheers,
>
> Mark
>
> On 28/06/06, Brett Porter <br...@apache.org> wrote:
>> Hi,
>>
>> Edwin has come up with this:
>> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>>
>> Any feedback before I apply it?
>>
>> - Brett
>>
>> --
>> Brett Porter <br...@apache.org>
>> Apache Maven - http://maven.apache.org/
>> Better Builds with Maven - http://library.mergere.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Mark Hobson <ma...@gmail.com>.
Definitely a big improvement :)
I agree that it'd be nice to see the default value for optional
parameters in the table. Perhaps append it to the description, e.g.
appendAssemblyId boolean Set to false to exclude the assembly id
from the assembly final name. (Default value is true)
Also it'd be nice at least to link complex object types to their
javadoc, e.g. MavenArchiveConfiguration in maven-jar-plugin. An
example XML block from introspecting the bean would be even better ;)
Cheers,
Mark
On 28/06/06, Brett Porter <br...@apache.org> wrote:
> Hi,
>
> Edwin has come up with this:
> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>
> Any feedback before I apply it?
>
> - Brett
>
> --
> Brett Porter <br...@apache.org>
> Apache Maven - http://maven.apache.org/
> Better Builds with Maven - http://library.mergere.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Edwin Punzalan <ep...@exist.com>.
+1
I see no generated pages showing these anywhere... ( or am I blind? ^_^ )
Jesse McConnell wrote:
> could it show the class lvl phase and goal settings and perhaps if it
> requiresDependencyResolution and that sort of thing?
>
> nice improvement though :)
>
> jesse
>
> On 6/28/06, Brett Porter <br...@apache.org> wrote:
>> Hi,
>>
>> Edwin has come up with this:
>> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>>
>> Any feedback before I apply it?
>>
>> - Brett
>>
>> --
>> Brett Porter <br...@apache.org>
>> Apache Maven - http://maven.apache.org/
>> Better Builds with Maven - http://library.mergere.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: generated plugin documentation: opinions?
Posted by Jesse McConnell <je...@gmail.com>.
could it show the class lvl phase and goal settings and perhaps if it
requiresDependencyResolution and that sort of thing?
nice improvement though :)
jesse
On 6/28/06, Brett Porter <br...@apache.org> wrote:
> Hi,
>
> Edwin has come up with this:
> http://jira.codehaus.org/secure/attachment/21233/assembly-mojo.html
>
> Any feedback before I apply it?
>
> - Brett
>
> --
> Brett Porter <br...@apache.org>
> Apache Maven - http://maven.apache.org/
> Better Builds with Maven - http://library.mergere.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
jesse mcconnell
jesseDOTmcconnellATgmailDOTcom
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org