mvn site
"?[top] |
You can integrate your static pages by following these steps:
${basedir}/src/site/resources
site.xml
and put it in ${basedir}/src/site
[top] |
This happens because the Site Plugin tries to make all URLs relative,
when possible. If you have something like this defined in your
pom.xml
:
<url>http://www.your.site.com/</url>
site.xml
(just an example) like
this:
<links> <item></item> <item></item> </links>
There is an issue for this in JIRA, where you can read more about this.
[top] |
mvn site
"?
What "mvn site
" will do for you, in a multi-project
build, is to run "mvn site
" for the parent and all its
modules individually. The links between parent and child will
not work here. They will however work when you deploy
the site.
If you want to test this, prior to deployment, you can run the
site:stage
goal as
described in the usage documentation
instead.
[top] |
The site plugin handles out-of-box apt, xdoc and fml formats. If you want to use a custom format like Twiki, you need to specify the Doxia Twiki dependency, i.e.:
<project> ... <build> <plugins> ... <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-site-plugin</artifactId> <dependencies> <dependency> <groupId>org.apache.maven.doxia</groupId> <artifactId>doxia-module-twiki</artifactId> <version>1.0</version> </dependency> </dependencies> </plugin> </plugins> </build> ... </project>
[top] |