On 11/29/05, Sean Schofield <[EMAIL PROTECTED]> wrote:

> I have a question about Maven website building.  It looks like our
> subprojects match up pretty nicely with the Maven "module" concept but
> I'm wondering what the final website will look like.  Is it possible
> to link modules into your top level module and site?  It looks like
> maybe you can from what the Struts team has done.

Keep in mind, that's a Maven 1 site.  I haven't quite managed to
convince m2 to do the same thing, but I'm getting closer.

Watch out for http://jira.codehaus.org/browse/MNG-661, m2 will build
the site for each module, but won't aggregate it so you can preview
it.  (Fix version 2.0.1?  I never know whether that means it's already
fixed, or planned to be... different projects seem to use it in
different ways.)

> There are certain items that I think should be generated at the top
> project level (list of contributors, mailing lists, issue tracking,
> etc.)

Those come from the Project Info Plugin.  Looks like you can pick what
things show up there:
  http://maven.apache.org/plugins/maven-project-info-reports-plugin/howto.html
(Suppressing this at the module level doesn't make sense-- it's where
'Dependencies' will appear, and those will be different for each
module.)

> Then there are other items that would be nice to have at the
> subproject level (javadocs, general overview and unit tests.)  What
> are the options with Maven as far as this goes?

Those show up in "Project Reports" and are also configured in
the<reporting> section.  For example, to get CheckStyle:
    <reporting>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-checkstyle-plugin</artifactId>
                <version>2.0-beta-1</version>
            </plugin>
        </plugins>
    </reporting>

HTH,
--
Wendy

Reply via email to