Wendy Smoak wrote:
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?
I'll see what I can do, thanks for the pointers, and at least I feel
less alone now :)
"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.
Yes, I do use <dependencyManagement>. I tried "mvn site -U" and it still
fails. So I can't use <dependencyManagement>? That would suck...
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.
Yes, I am slowly discovering that the deploy part of the lifecycle is
essential, for other stuff too...
--
cg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
