you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.

2009/8/14 David Hoffer <[email protected]>:
> This works for us, try this in your parent pom:
>
> <build>
>                <plugins>
>                    <plugin>
>                        <groupId>org.apache.maven.plugins</groupId>
>                        <artifactId>maven-javadoc-plugin</artifactId>
>                        <version>2.5</version>
>                        <executions>
>                            <execution>
>                                <id>attach-javadocs</id>
>                                <goals>
>                                    <goal>jar</goal>
>                                </goals>
>                            </execution>
>                        </executions>
>                    </plugin>
>                </plugins>
>            </build>
>
> <reporting>
> ...
> <plugin>
>                <!--Provides javadocs-->
>                <groupId>org.apache.maven.plugins</groupId>
>                <artifactId>maven-javadoc-plugin</artifactId>
>                <version>2.5</version>
>                <configuration>
>                    <aggregate>true</aggregate>
>                </configuration>
>            </plugin>
>
> </reporting>
>
> -Dave
>
> On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack <
> [email protected]> wrote:
>
>> Hi all,
>>
>> My first maven project, plain JavaSE. I want to build javadoc jars,
>> independent of any site - I'm trying to get that working as well, but for
>> now I'm considering them separately.
>>
>> For organisation purposes, I've split my work into several projects, which
>> I've now made modules of a parent. Creating a source bundle with
>> source:aggregate (having also done source:jar-no-fork on the modules) was
>> easy. Now I want to create a combined javadoc bundle, and that's not proving
>> easy.
>>
>> I've successfully got javadoc:jar running on the modules. However,
>> javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
>>
>> Now, since I'm using m2eclipse, I can happily create a javadoc by running
>> the eclipse javadoc builder over multiple projects, but I'd rather integrate
>> with maven if at all possible. Anyone have any ideas?
>>
>>
>> --
>> Sam Barnett-Cormack
>>
>> ---------------------------------------------------------------------
>> 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