Hi,
I use Maven 1.0.2 (what I've used for the last 4 yrs ... since it works and I
don't trust the (lack of) backwards compatibility concerns of the Maven
project
> I see the same error as Craig if I run 'maven site' in jdo/site. I also
> have a site.jsl in my
> .maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources. But there is a
> (different) site.jsl checked in into jdo/site/xdocs. In addition the
> file project.properties in jdo/site defines a property
> 'maven.xdoc.jsl=xdocs/site.jsl'. If I delete this property 'maven site'
> succeds.
There is a different "site.jsl" checked in to xdocs because that is there to
override the default site generation of Maven1. Without it you get a chunky
site with none of the refinements that were added ;-)
maven-xdoc-plugin is *supposed* to allow overriding the default stylesheet via
the property "maven.xdoc.jsl" (not that they can be bothered to document
it) ... hence why it is in project.properties pointing to ours. It currently
doesn't have ${basedir} prepended and maybe should have (but that doesn't
solve this issue anyway so ignore that).
The maven-xdoc-plugin bundled with Maven1.0.2 accepts that overriding. The one
that comes with Maven1.1 accepts it so far (since it even prints out
the "site.jsl" it will use ... correctly) but then tries to append that name
on the end of the plugin workspace!!! duh.
If you chase the process through the plugin.jelly of that plugin you get to
<x:parse var="doc" xml="${file}"/>
<j:file name="${outFile}" encoding="${outputencoding}"
omitXmlDeclaration="true" outputMode="xml"
prettyPrint="no">
<j:include uri="${stylesheet.toString()}"/>
</j:file>
which has the correct stylesheet name going in (ours). Where that then goes to
I've no idea.
Maybe some Maven team member could comment, and there's some secret setting
that you have to use to get it to work with your own site.jsl file in Maven
1.1 ?
--
Andy (Java Persistent Objects - http://www.jpox.org)
