[
https://issues.apache.org/jira/browse/MSITE-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677505#comment-17677505
]
Michael Osipov commented on MSITE-922:
--------------------------------------
Just tried, works fine for me:
{noformat}
osipovmi@deblndw011x:~/var/Projekte/antisamy (main *=)
$ git diff
diff --git a/pom.xml b/pom.xml
index 08a4ce8..3c1f03c 100644
--- a/pom.xml
+++ b/pom.xml
@@ -391,7 +391,7 @@
being used is documented here, but unforunately it has to
be specified in the site.xml specifically. -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
- <version>4.0.0-M3</version>
+ <version>4.0.0-M4</version>
<!-- version>4.0.0-M4</version - Upgrading to this version
breaks the tables in many of the generated pages for some reason but
4.0.0-M3 works fine. -->
</plugin>
diff --git a/src/site/site.xml b/src/site/site.xml
index cf9c6ad..2e4b618 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -10,7 +10,7 @@
<groupId>org.apache.maven.skins</groupId>
<artifactId>maven-fluido-skin</artifactId>
<!-- NOTE: The version has to be specified here as it apparently is
NOT inherited from the pom file. -->
- <version>1.11.1</version>
+ <version>2.0.0-M2</version>
</skin>
<custom>
<fluidoSkin>
{noformat}
> Using 4.0.0-M4 w/ maven-fluido-skin breaks table formatting in generated
> pages
> -------------------------------------------------------------------------------
>
> Key: MSITE-922
> URL: https://issues.apache.org/jira/browse/MSITE-922
> Project: Maven Site Plugin
> Issue Type: Bug
> Affects Versions: 4.0.0-M4
> Reporter: Dave Wichers
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> If, after you set the maven-site-plugin version to 4.0.0-M4 in the AntiSamy
> ([https://github.com/nahsra/antisamy]) pom.xml, you run: 'mvn site' against
> the main branch of this project:
> It generates the site docs just fine, but the tables are broken in many of
> the pages, which are rendered fine with the 4.0.0-M3 version of the
> maven-site-plugin.
> I did the following diff of 1 broken vs. OK generated site page file and
> here's what it shows:
> antisamy % diff target/site/spotbugs.html ../targetBroken/site/spotbugs.html
> 5c5
> {quote}< | Generated by Apache Maven Doxia Site Renderer 1.11.1 from
> com.github.spotbugs:spotbugs-maven-plugin:4.7.3.0:spotbugs at 2023-01-16
> ---
> > | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from
> >com.github.spotbugs:spotbugs-maven-plugin:4.7.3.0:spotbugs at 2023-01-16
> 8c8
> < <html xmlns="http://www.w3.org/1999/xhtml"; lang="en">
> ---
> > <html xmlns="http://www.w3.org/1999/xhtml"; lang="">
> 12c12
> < <meta name="generator" content="Apache Maven Doxia Site Renderer
> 1.11.1" />
> ---
> > <meta name="generator" content="Apache Maven Doxia Site Renderer
> > 2.0.0-M4" />
> 70c70
> < <h2><a name="SpotBugs_Bug_Detector_Report"></a>SpotBugs Bug Detector
> Report</h2>
> ---
> > <h1>SpotBugs Bug Detector Report</h1>
> 75,76c75
> < <h2><a name="Summary"></a>Summary</h2>
> < <table border="0" class="table table-striped">
> ---
> > <h1>Summary</h1>
> 87,88c86
> < <h2><a name="Files"></a>Files</h2>
> < <table border="0" class="table table-striped">
> ---
> > <h1>Files</h1>
> 97,99c95,96
> < <td>1</td></tr></table></section><a
> name="org.owasp.validator.css.CssHandler"></a><section>
> < <h3><a
> name="org.owasp.validator.css.CssHandler"></a>org.owasp.validator.css.CssHandler</h3>
> < <table border="0" class="table table-striped">
> ---
> > <td>1</td></tr></table></section><a
> > id="org.owasp.validator.css.CssHandler"></a><section>
> > <h2>org.owasp.validator.css.CssHandler</h2>
> 123,125c120,121
> < <td>Medium</td></tr></table></section><a
> name="org.owasp.validator.css.CssScanner"></a><section>
> < <h3><a
> name="org.owasp.validator.css.CssScanner"></a>org.owasp.validator.css.CssScanner</h3>
> < <table border="0" class="table table-striped">
> ---
> > <td>Medium</td></tr></table></section><a
> > id="org.owasp.validator.css.CssScanner"></a><section>
> > <h2>org.owasp.validator.css.CssScanner</h2>
> {quote}
> Given that it works with 4.0.0-M3 this seems like a bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
