[
http://jira.codehaus.org/browse/MSITE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220313#action_220313
]
Andrew Hughes commented on MSITE-477:
-------------------------------------
Currently running with maven 2.2.1, and maven-site-plugin 2.0.1 on Windows XP
(32bit).
{noformat}
<distributionManagement>
<!--
We don't have anywhere to deploy site releases too (no ftp
or scp or svn). But we still want to use site:stage-deploy
for the hudson builds. These param's are needed by the site
plugin, but will be by-passed by...
<stagingSiteURL>file://...../${project.groupId}</stagingSiteURL>
So add that as a property in a profile if you want to deploy
sites.
-->
<site>
<id>site</id>
<name>site</name>
<url>placeholder-only</url>
</site>
</distributionManagement>
<reporting>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<configuration>
<includeTestSourceDirectory>true</includeTestSourceDirectory>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
<version>2.0.1</version>
<configuration>
<findbugsXmlOutput>true</findbugsXmlOutput>
<findbugsXmlWithMessages>true</findbugsXmlWithMessages>
<xmlOutput>true</xmlOutput>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>taglist-maven-plugin</artifactId>
</plugin>
<plugin>
<artifactId>maven-surefire-report-plugin</artifactId>
<version>2.4.2</version>
</plugin>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<source>${maven.compiler.source}</source>
<maxmemory>512m</maxmemory>
<useStandardDocletOptions>true</useStandardDocletOptions>
<!--
The following configuration adds support for uml
class diagrams in the javadocs. This is done via
UmlGraph and the Dotuml plugin (upstream). In
order for these two plugins to work graphviz
needs to be installed on the machine running it
and ./Graphviz2.26.3/bin to be on the system
PATH. If you don't have this the build will
still work, but the diagrams will be missing.
-->
<doclet>gr.spinellis.umlgraph.doclet.UmlGraphDoc</doclet>
<docletArtifact>
<groupId>gr.spinellis</groupId>
<artifactId>UmlGraph</artifactId>
<version>4.6</version>
</docletArtifact>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<configuration>
<targetJdk>${maven.compiler.target}</targetJdk>
</configuration>
</plugin>
</plugins>
</reporting>
{noformat}
I am not providing a site.xml, ./src/site is completely empty. The project does
not have a parent.
The only *strange* thing I am doing is asking hudson to deploy the site with
the following goals:
{noformat}
clean install site site:stage-deploy
-DstagingSiteURL=file://e:/Data/Apache/sites/com.acme.project
{noformat}
But, I doubt that any of the above configuration has anything todo with the
generated module href's.
> <menu ref="modules"/> href's drop the leading character in the href
> -------------------------------------------------------------------
>
> Key: MSITE-477
> URL: http://jira.codehaus.org/browse/MSITE-477
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
> Affects Versions: 2.0.1, 2.1
> Reporter: Andrew Hughes
>
> parent pom.xml:
> {noformat}
> <module>module-a</modules>
> {noformat}
> parent site.xml:
> {noformat}
> <menu ref="modules"/>
> {noformat}
> The generated html links to "module-a" look like this....
> {noformat}
> <a href="odule-a/index.html" title="module-a">module-a</a>
> {noformat}
> Note, the href is missing the leading character "m", it should be..
> {noformat}
> <a href="module-a/index.html" title="module-a">module-a</a>
> {noformat}
> I tried to run this wil 2.0.1 and 2.1 - but got the same result with both.
> Hopfully this is a mis-configuration on my part, but if it is then perhaps it
> can be tested by the plugin and can fail the build.
> Thanks for reading :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
