Wendy Smoak wrote:
On 4/14/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
... to get the Javadoc generated for the
site, add this to action/pom.xml:

<reporting>
      <plugins>
         <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>
               <configuration>
                   <aggregate>true</aggregate>
               </configuration>
        ...

I built the javadoc plugin to try the aggregation feature, which
partially works.  It builds the aggregated Javadoc fine, but then
fails afterwards.  Brett is aware of it and
http://jira.codehaus.org/browse/MJAVADOC-66 has been opened.

Looking at the output, which I'll post an example of tonight, I think
we need to re-package the app that's using the "example" package.
(Cookbook?)  It looks strange in the consolidated list of packages.

Don/James... do you want to pull all the xdocs up from the sub-modules
of Action and have them all in action/trunk/src/site/ ?  I would
imagine that eventually, all the reports (JUnit test results, etc.,)
will be able to be aggregated and the sub-sites wouldn't be necessary.

Yeah, I thought about that, but how would it work with generated docs like taglib docs? We definitely need an action/src/site directory to contain the root site.xml that others inherit, and if you can get over the aforementioned issue, then collecting all docs there would work for me. Especially since we don't necessarily want the Action 1 site to be a reflection of the multiple artifacts, but rather appear as one product.

I'm not sure yet, but making Action's 'site' a module might work
better:  action/trunk/site/src/site.  The WADI incubator project has a
similar structure and might be worth looking at:
http://svn.apache.org/repos/asf/incubator/wadi/trunk/

Whatever works :)

Don


--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to