From: "Jay H. Hartley" <[EMAIL PROTECTED]>
You mention that you "need" to have the documentation as part of the root
web site. Would having it one link down but clearly labeled at the top of
the sub-project list satisfy the need?
No, the files really need to be up at the top level. I'm integrating the
existing Struts site into the Maven-generated multi-project site, and I
don't want to break all the links that are already out there. It's looking
good so far... I just wanted to be sure I wasn't doing more work than
necessary in navigation.xml. :)
Another multiproject site question: Is there a way to override the
directory name that 'multiproject:site' comes up with for each subproject?
It seems to be coming from the <id> tag in project.xml. Some of the <id>s
don't match the directory names we've been using for those projects, but
they are correct for use in the .jar file name.
For example, the Struts Flow website is http://struts.apache.org/flow, yet
its <id> is 'struts-flow'. Once the documentation gets pushed down under
/struts/current/flow/xdocs, I need to retain the directory name for the
website, yet the .jar file needs to be struts-flow-x.x.x.jar.
There's a property for everything else. :) But I don't see anything
relevant on http://maven.apache.org/reference/plugins/site/properties.html
Is this possible to override, or is the answer possibly as simple as a
postGoal to rename the directory?
Thanks,
--
Wendy Smoak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
