Hi
When using the current version of the site plugin and running site:site on
the root/parent module, the site plugin will process the child modules as
well.
When deploying the site the child modules site will be but in the parent
modules site directory under the name of the artifactId.
Ex:
project setup:
parent-module/
child-module1
child-module2
deployed site:
parent/
[child-module1-artifactid]/
[child-module2-artifactid]/
So it is known how to hyperlink to the child modules from the parent module.
But it isn't possible to properly test it without deploying the site,
because the location the sites are in the children's taget directories.
With the next release of the site plugin there seems to be a ${modules}
expression which will generate navigation to the children, but I haven't
tested this yet. It is probably worthwhile for you to add the apache plugin
snapshot repository to your configuration and set the version of the site
plugin to 2.0-SNAPSHOT (and run a mvn -U ) which will (probably) give you
the ${modules} feature (not sure about this since I haven't tested it yet
myself).
Hope this helps a little
- Micke
On 03/05/06, Dan Adams <[EMAIL PROTECTED]> wrote:
I have a project that has multiple modules to it and would like to
produce a site that ties the modules together. Can anyone point me to a
good example of how do to things like easily provide a consistent header
to all the sub-module sites?
--
Dan Adams
Software Engineer
Interactive Factory
617.235.5857
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
