This took quite a lot of messing around in Seam's distribution build thanks to Maven's lack of support for multi-module projects.  To point you in the right direction, take a look at:

https://github.com/seam/dist/blob/master/dist/pom.xml

Down near the end of the pom you'll find this plugin configuration:

         <plugin>         
            &!
 lt;groupId
>org.apache.maven.plugins</groupId>
            <artifactId>maven-dependency-plugin</artifactId>
            <executions>
       !
 ; &nb
sp;      <execution>
                  <id>module-sources</id>
                  <goals>
&nbs
p;                    <goal>unpack-dependencies</goal>
                  </goals>
                  <configuration>
                     <classifier>sources</classifier>
                     <outputDirectory>${project.build.directory}/sources</outputDirectory>
                     <excludeTransitive>true</excludeTransitive>
                     
                     <includeArtifactIds>seam-face
s-api,seam-international-api,seam-jcr-api,seam-jms-api,seam-mail-api,seam-persistence-api,seam-remoting,seam-reports-api,seam-rest-api,seam-security-api,seam-social-api,seam-social,seam-transaction-api,seam-validation-api,solder-api</includeArtifactIds>
                  </configuration>
               </execution>

And a little further down you'll find this:

         <plugin>
            <artifa!
 ctId>maven-javadoc-plugin</artifactId>
            <version>2.7</version>
            
            <executions>
               <execution>
                  <id>javadoc-jar</id>
                  <phase>package</phase>
                  <goals>
                     <goal>jar</goal>
                  </goals>
                  <configuration>
                     <sourcepath>${project.build.directory}/sources</sourcepath>
                     <links>
                       <link>http://download.oracle.com/javaee/6/api</link>
                       <link>http://download.oracle.com/javase/6/docs/api/</link>
                     </links>
     &nb!
 sp; &
nbsp;             
                     <keywords>true</keywords>
                     <author>true</author>
!
 
                  </configuration>
               </execution>
            </executions>
!
  &nbs
p;       </plugin> 

What the first bit does is essentially unpacks the entire source tree for all Seam modules into a single directory structure.  The second bit runs the javadoc plugin over this unpacked source code, creating the "consolidated" javadocs for the entire project.  It's a little convoluted however there didn't seem to be any easier way to do this.

Shane

On 11/10/12 08:14, Ivan St. Ivanov wrote: