[ http://jira.codehaus.org/browse/MCLOVER-47?page=all ]

Franz Allan Valencia See updated MCLOVER-47:
--------------------------------------------

    Attachment: MCLOVER-47-maven-clover-plugin-3.patch

Good day to you, Vincent,

I see your point there. In line with that, I placed all the examples back to 
the "Usage" section. However, the organization and some wording have changed. I 
first introduced the Instrumentation (in the guise of "Getting Started") and 
then followed it up by Checking test coverage, then Generating a clover report, 
then the rest. Furthermore, I made some parts into subsections of others. The  
main sections are the usual use cases (except for the last part...but since I 
can't seem to find a main section to put it under, I simply made it into a main 
section) while the subsections are the not so often use cases. (btw, I've also 
fixed the table of contents links and added a "back to top".)

Furthermore, I changed the Introduction page to match those of the other plugin 
documentations. Meaning I made some format changes, and added the Goals 
section. But I did retain your Features section and I no longer modified your 
Examples section.

Maybe we should try and finish this first before raising it in the dev list so 
that we can stage this up to give the community of the plugin documentation we 
would be proposing

WDYT?

Thanks,
Franz

> Align plugin documentation with Maven standards
> -----------------------------------------------
>
>                 Key: MCLOVER-47
>                 URL: http://jira.codehaus.org/browse/MCLOVER-47
>             Project: Maven 2.x Clover Plugin
>          Issue Type: Task
>    Affects Versions: 2.2
>            Reporter: John Tolentino
>         Assigned To: Vincent Massol
>             Fix For: 2.3
>
>         Attachments: MCLOVER-47-maven-clover-plugin-2.patch, 
> MCLOVER-47-maven-clover-plugin-3.patch, MCLOVER-47-maven-clover-plugin.patch
>
>
> http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to