Georg Kallidis created MSKINS-254:
-------------------------------------
Summary: Rendering tabel in section from changes-report
Key: MSKINS-254
URL: https://issues.apache.org/jira/browse/MSKINS-254
Project: Maven Skins
Issue Type: Bug
Components: Fluido Skin
Affects Versions: fluido-2.0.0-M11, fluido-2.0.0-M9
Reporter: Georg Kallidis
When running in a project with src/changes/changes.xml
{code:sh}
mvn changes:changes-report
{code}
does generate correct html code
{code:html}
<!-- Generated by Apache Maven Doxia Site Renderer 1.4 at 2024-10-10 -->
....
<div class="section">
<h3>Release-Geschichte<a name="Release-Geschichte"></a></h3>
<table border="0" class="bodyTable">
<tr class="a">
<th>Version</th>
..
{code}
but when running
{code:sh}
mvn site
{code}
the result is missing the table element after the section element.
{code:html}
<!--
| Generated by Apache Maven Doxia Site Renderer 2.0.0-M19 from
org.apache.maven.plugins:maven-changes-plugin:2.12.1:changes-report at
2024-10-10
| Rendered using Apache Maven Fluido Skin 2.0.0-M9
-->
..
</header>
<main id="bodyColumn" class="span10">
<section>
<h1>Changes</h1><section>
<h2>Release History</h2>
<tr class="a">
<th>Version</th>
<th>Date</th>
<th>Description</th></tr>
<tr class="b">
..
..
{code}
Though I only checked that in maven-fluido-skin resources/META-INF/site.vm
*$bodyColumn* {*}already contains the wrong body content missing the table
element{*}.
I am currently unable to understand exactly the mechanism, where the
transformation comes from doxia site tool and which template are used get this
done.
Is it a fluido skin ( 2.0.0-M9 or 2.0.0-M11 does makes no difference) or does
it happen still more upstreams?
It might be doxia tools ..
Example changes.xml:
{code:xml}
<document>
<properties>
<title>Changes</title>
</properties>
<body>
<release version="1.0.0-SNAPSHOT" date="in Git">
<action type="update" dev="foo">bar
</action>
</release>
</body>
</document>
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
