There has been an ongoing discussion about this on the Maven users list. See
http://mail-archives.apache.org/mod_mbox/maven-users/200701.mbox/%3c8236846.post@talk.nabble.com%3e
and
http://mail-archives.apache.org/mod_mbox/maven-users/200701.mbox/%3c8268299.post@talk.nabble.com%3e

In short - I have not been able to reproduce this using doxia HEAD, or any other version for that matter.

That is because, an empty POM DOES work. Which is scary. Really scary. The following result was rendered using attached POM 1:

<a name="section_1"></a><div class="section"><h2>section 1</h2>
<p>text 1</p>
<ul>
<li>list1</li>
</ul>
<p>text 2</p>
<ul>
<li>list1</li>
</ul>
<p>text 3</p>
</div>

And this using the attached POM 2:

<a name="section 1"></a><div class="section"><h2>section 1</h2>
<p>text 1</p>
<ul>
<li>list1</li>
</ul>
text 2
<ul>
<li>list1</li>
</ul>
text 3
</div>

The difference is the configured extension. You can get that from http://velocity.apache.org/site/tools/velocity-site-doxia-renderer/index.html or just drop me a mail. (I will put it into the apache repository once we got velocity 1.5 out of the door).

working POM.

non working POM.

Ah, I forgot to mention, that I've added the DTD reference for XDOC to the source file and it is valid.

It seems that maven dependency resolution fooled me. = The extension pulls in an explicit version of the doxia core (1.0-alpha-8). Once I forced it to actually use the HEAD (1.0-alpha-9-SNAPSHOT), it now renders correctly.

Also fixed in unreleased 1.0-alpha-9, however that version is missing from JIRA.

Just for fun I add another test case to prove you that all is already fixed in the trunk