On 12/5/06, Christian Goetze <[EMAIL PROTECTED]> wrote:
If I generate the default site according to the mergere book, I get
essentially a useless cover page with a navigation menu that lists the
modules, but without links
I've seen that happen too. Most of my projects have a custom site.xml
and aren't using ${modules} (?) though, so I've never tried to chase
it down. Can you reproduce it with a simple parent-and-two-children
multi-module project?
"mvn site" fails with an internal error, stumbling over a dependency
which seems to stem from the java code being javadoc'ed itself.
Are you using <dependencyManagement> ? This sounds familiar, but I
thought it was fixed. First try 'mvn site -U' to make sure you've got
the latest plugin versions, or (better) add a <version> element to set
the version you want to use.
If I set it to false, I don't see any link or anything at all.
Javadoc will be under 'Project Reports' at the bottom of the menu. Do
you have ${reporting} (or possibly ${reports}) in site.xml?
Is the intent to let maven generate some of the pages, and I need to add
the static pages linking them all together myself?
Not sure what you mean here... 'mvn site' is only going to generate
the pieces of a multi-module site under the various 'target'
directories. To see what the whole thing looks like you'll need to
use either site:stage or site:deploy.
The default index.html page will include the <description> from the
pom, if you want more than that, add src/site/apt/index.apt with your
content.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
