If I understand correctly, Maven always uses it's embedded version of
doxia, which you can't override (see [1]).
If you want to test the docbook generation, you should add some docbook
sources to the tests in doxia-site-renderer [2], ie in
src/test/site/docbook/ and assert the generated files when running test.
(And don't forget to submit your tests to jira if it works!). Note also
the currently known issues with the docbook module: [3].
HTH,
-Lukas
[1]
http://jira.codehaus.org/browse/MNG-3402[2]
http://svn.apache.org/viewvc/maven/doxia/doxia-sitetools/trunk/doxia-site-renderer/[3]
http://jira.codehaus.org/browse/DOXIA-184Max Berger wrote:
> Dear Developers,
>
> I've recently discovered that the doxia maven plugin fails to convert
> docbook source files to html pages on one of my machines (OS X running
> Apples JVM 1.5.0_13). These files are ignored, as if they would not
> exist. However, using the same pom and same maven version (2.0.8), the
> website renders fine under Linux. Also, APT files render just fine. No
> error message is printed, the docbook files are just silently ignored.
>
> I wanted to look at the source doxia-module-docbook-simple, and I found
> and compiled doxia trunk (the whole package) sucessfully. However, I
> failed to find information how to install the updated plugin into my
> installation: A simple "mvn install" will install the new doxia
> artifacts, but not use them. I tried adding
> <plugin>
> <groupId>org.apache.maven.doxia</groupId>
> <artifactId>doxia-maven-plugin</artifactId>
> <version>1.0-beta-1-SNAPSHOT</version>
> </plugin>
>
> to the pom, which did not help either. How can I tell maven to use the
> new doxia version?
>
>
> mfG
>
> Max Berger
> e-mail:
max@...
>
