[ 
http://jira.codehaus.org/browse/MPLUGIN-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227022#action_227022
 ] 

Anton Kronseder commented on MPLUGIN-165:
-----------------------------------------

Just tried it with maven-site-plugin 2.2-SNAPSHOT: this error still exists.

The maven-plugin-plugin creates the page source with table align="left" as to
org.apache.maven.tools.plugin.generator.PluginXdocGenerator line 665 of 
maven-plugin-tools-api project,
but the maven-site-plugin <= 2.0.1 does not copy this (align="left") to the 
.html files in target/site.

Using maven-site-plugin >= 2.1 up to 2.2-SNAPSHOT maven site seems to handle 
the source-files containing the align="left" different and copies this to the 
output .html files.

This leads to the missing space between the table and the following h3 
(contained in the section div).
(see the Image and the missing space between "Optional Parameters" and the 
table of "Required Parameters").




> Upgrading to Maven Site 2.1 messes up plugin site generation
> ------------------------------------------------------------
>
>                 Key: MPLUGIN-165
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-165
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 2.5.1
>            Reporter: Mike Youngstrom
>         Attachments: deployable-mojo.html, plugin-report.jpg
>
>
> If I upgrade my site plugin to 2.1 then my plugin sites get all messed up.  
> Two problems I noted in particular include:
> 1. The Report links aren't rendered at all on the left side of the screen.
> 2. The plugin goal detail page layout is messed up.  headers don't align with 
> backgrounds for headers.

-- 
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