You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Sam Barnett-Cormack <s....@lancaster.ac.uk> on 2009/08/14 13:00:59 UTC
javadoc plugin aggregation woes
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by David Hoffer <dh...@gmail.com>.
I might add, we do also run site-deploy which takes the javadocs and adds to
the site generated.
-Dave
On Fri, Aug 14, 2009 at 8:21 AM, David Hoffer <dh...@gmail.com> wrote:
> No any call to install or deploy will build it. This isn't required but we
> do wrap the build section in a profile so we only do this on the CI
> system...as this takes a while.
>
> -Dave
>
>
> On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
> s.barnett-cormack@lancaster.ac.uk> wrote:
>
>> David Hoffer wrote:
>>
>>> This works for us, try this in your parent pom:
>>>
>>
>> When running this, does it need site:site running to build the javadoc
>> before running a build that'll generate the jar?
>>
>>
>> <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 <
>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>
>> --
>> Sam Barnett-Cormack
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
Ah, switch the aggregator to do aggregate-jar and it all works now
(afaict). Nice.
Sam Barnett-Cormack wrote:
> David Hoffer wrote:
>> I don't know about running from the command line...we have our CI system
>> auto deploy javadocs/source jars to our internal repo so IDE's get this
>> integrated with the binaries. This is the functionality I was looking
>> for.
>
> Well, I'm getting the website combined javadocs, and I'm getting the
> per-module jar'ed javadocs, but not the combined jar'ed javadocs,
> because of the message below (afaict). Anyone know how I'd bring this to
> the attention of the devs of the maven-javadoc-plugin?
>
>> On Fri, Aug 14, 2009 at 8:29 AM, Sam Barnett-Cormack <
>> s.barnett-cormack@lancaster.ac.uk> wrote:
>>
>>> David Hoffer wrote:
>>>
>>>> No any call to install or deploy will build it. This isn't required
>>>> but
>>>> we
>>>> do wrap the build section in a profile so we only do this on the CI
>>>> system...as this takes a while.
>>>>
>>> Well, that works very well for putting the aggregated javadoc on the
>>> generated site (once I configured it to generate a site), but the
>>> attempt to
>>> javadoc:jar gives me:
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Building ASN.1 Java Implementation
>>> [INFO] task-segment: [javadoc:jar]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
>>> <code>javadoc
>>> :aggregate</code> and
>>> <code>javadoc:test-aggregate</code> instead.
>>> [INFO] [javadoc:jar {execution: default-cli}]
>>> [INFO] Not executing Javadoc as the project is not a Java
>>> classpath-capable
>>> package
>>>
>>> The deprecation I can deal with later, but the not-running-javadoc is a
>>> pain.
>>>
>>>
>>> On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
>>>> s.barnett-cormack@lancaster.ac.uk> wrote:
>>>>
>>>> David Hoffer wrote:
>>>>> This works for us, try this in your parent pom:
>>>>>> When running this, does it need site:site running to build the
>>>>>> javadoc
>>>>> before running a build that'll generate the jar?
>>>>>
>>>>>
>>>>> <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 <
>>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>> Sam Barnett-Cormack
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>> --
>>> Sam Barnett-Cormack
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>
>
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
David Hoffer wrote:
> I don't know about running from the command line...we have our CI system
> auto deploy javadocs/source jars to our internal repo so IDE's get this
> integrated with the binaries. This is the functionality I was looking for.
Well, I'm getting the website combined javadocs, and I'm getting the
per-module jar'ed javadocs, but not the combined jar'ed javadocs,
because of the message below (afaict). Anyone know how I'd bring this to
the attention of the devs of the maven-javadoc-plugin?
> On Fri, Aug 14, 2009 at 8:29 AM, Sam Barnett-Cormack <
> s.barnett-cormack@lancaster.ac.uk> wrote:
>
>> David Hoffer wrote:
>>
>>> No any call to install or deploy will build it. This isn't required but
>>> we
>>> do wrap the build section in a profile so we only do this on the CI
>>> system...as this takes a while.
>>>
>> Well, that works very well for putting the aggregated javadoc on the
>> generated site (once I configured it to generate a site), but the attempt to
>> javadoc:jar gives me:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building ASN.1 Java Implementation
>> [INFO] task-segment: [javadoc:jar]
>> [INFO]
>> ------------------------------------------------------------------------
>> [WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
>> <code>javadoc
>> :aggregate</code> and
>> <code>javadoc:test-aggregate</code> instead.
>> [INFO] [javadoc:jar {execution: default-cli}]
>> [INFO] Not executing Javadoc as the project is not a Java classpath-capable
>> package
>>
>> The deprecation I can deal with later, but the not-running-javadoc is a
>> pain.
>>
>>
>> On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
>>> s.barnett-cormack@lancaster.ac.uk> wrote:
>>>
>>> David Hoffer wrote:
>>>> This works for us, try this in your parent pom:
>>>>> When running this, does it need site:site running to build the javadoc
>>>> before running a build that'll generate the jar?
>>>>
>>>>
>>>> <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 <
>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>> Sam Barnett-Cormack
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>> --
>> Sam Barnett-Cormack
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by David Hoffer <dh...@gmail.com>.
I don't know about running from the command line...we have our CI system
auto deploy javadocs/source jars to our internal repo so IDE's get this
integrated with the binaries. This is the functionality I was looking for.
-Dave
On Fri, Aug 14, 2009 at 8:29 AM, Sam Barnett-Cormack <
s.barnett-cormack@lancaster.ac.uk> wrote:
> David Hoffer wrote:
>
>> No any call to install or deploy will build it. This isn't required but
>> we
>> do wrap the build section in a profile so we only do this on the CI
>> system...as this takes a while.
>>
>
> Well, that works very well for putting the aggregated javadoc on the
> generated site (once I configured it to generate a site), but the attempt to
> javadoc:jar gives me:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building ASN.1 Java Implementation
> [INFO] task-segment: [javadoc:jar]
> [INFO]
> ------------------------------------------------------------------------
> [WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
> <code>javadoc
> :aggregate</code> and
> <code>javadoc:test-aggregate</code> instead.
> [INFO] [javadoc:jar {execution: default-cli}]
> [INFO] Not executing Javadoc as the project is not a Java classpath-capable
> package
>
> The deprecation I can deal with later, but the not-running-javadoc is a
> pain.
>
>
> On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
>> s.barnett-cormack@lancaster.ac.uk> wrote:
>>
>> David Hoffer wrote:
>>>
>>> This works for us, try this in your parent pom:
>>>>
>>>> When running this, does it need site:site running to build the javadoc
>>> before running a build that'll generate the jar?
>>>
>>>
>>> <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 <
>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>> --
>>> Sam Barnett-Cormack
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>
> --
> Sam Barnett-Cormack
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
David Hoffer wrote:
> No any call to install or deploy will build it. This isn't required but we
> do wrap the build section in a profile so we only do this on the CI
> system...as this takes a while.
Well, that works very well for putting the aggregated javadoc on the
generated site (once I configured it to generate a site), but the
attempt to javadoc:jar gives me:
[INFO]
------------------------------------------------------------------------
[INFO] Building ASN.1 Java Implementation
[INFO] task-segment: [javadoc:jar]
[INFO]
------------------------------------------------------------------------
[WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
<code>javadoc
:aggregate</code> and
<code>javadoc:test-aggregate</code> instead.
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
The deprecation I can deal with later, but the not-running-javadoc is a
pain.
> On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
> s.barnett-cormack@lancaster.ac.uk> wrote:
>
>> David Hoffer wrote:
>>
>>> This works for us, try this in your parent pom:
>>>
>> When running this, does it need site:site running to build the javadoc
>> before running a build that'll generate the jar?
>>
>>
>> <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 <
>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>> --
>> Sam Barnett-Cormack
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by David Hoffer <dh...@gmail.com>.
No any call to install or deploy will build it. This isn't required but we
do wrap the build section in a profile so we only do this on the CI
system...as this takes a while.
-Dave
On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack <
s.barnett-cormack@lancaster.ac.uk> wrote:
> David Hoffer wrote:
>
>> This works for us, try this in your parent pom:
>>
>
> When running this, does it need site:site running to build the javadoc
> before running a build that'll generate the jar?
>
>
> <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 <
>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>
> --
> Sam Barnett-Cormack
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
David Hoffer wrote:
> This works for us, try this in your parent pom:
When running this, does it need site:site running to build the javadoc
before running a build that'll generate the jar?
> <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 <
> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
David Hoffer wrote:
> 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>
Isn't that deprecated now? Just using the aggregate-jar target does no
good... I'll try using this. Maybe using the older version also helps.
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Stephen Connolly <st...@gmail.com>.
damn copy-pase
<project>
<parent>
<artifactId>project-parent</artifactId>
</parent>
<artifactId>project-complete</artifactId>
<modules>
<module>project-parent</module>
<module>project-a</module>
<module>project-b</module>
...
<module>project-e</module>
</modules>
<dependencies>
<dependency>
<artifactId>project-a</artifactId>
</dependency>
<dependency>
<artifactId>project-b</artifactId>
</dependency>
...
<dependency>
<artifactId>project-e</artifactId>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<inherited>false</inherited> <!-- not strictly speaking
necesary, but best practice as we are binding an aggregator goal -->
...
</plugin>
</plugins>
</build>
</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Stephen Connolly <st...@gmail.com>.
<project>
<parent>
<artifactId>project-parent</artifactId>
</parent>
<artifactId>project-___</artifactId>
<modules>
<module>project-parent</module>
<module>project-a</module>
<module>project-b</module>
...
<module>project-e</module>
</modules>
<dependencies>
<dependency>
<artifactId>project-a</artifactId>
</dependency>
<dependency>
<artifactId>project-b</artifactId>
</dependency>
...
<dependency>
<artifactId>project-e</artifactId>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<inherited>false</inherited> <!-- not strictly speaking
necesaary, but best practice as we are binding an aggregator goal -->
...
</plugin>
</plugins>
</build>
</project>
2009/8/14 Stephen Connolly <st...@gmail.com>:
> my understanding of aggregate is that it has to go where the <modules>
> (& by implication the dependencies) are
>
> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>> Ah. Exactly what I meant, but with the names complete and parent the other
>> way around. With the names your way around, the source and javadoc
>> aggregators would go in where?
>>
>> Stephen Connolly wrote:
>>>
>>> so to summarize:
>>>
>>> /project-complete
>>> +- project-parent
>>> +- project-a
>>> +- project-b
>>> ...
>>> \- project-e
>>>
>>> project-complete has the following
>>>
>>> <project>
>>> <parent>
>>> <artifactId>project-parent</artifactId>
>>> </parent>
>>> <artifactId>project-___</artifactId>
>>> <modules>
>>> <module>project-parent</module>
>>> <module>project-a</module>
>>> <module>project-b</module>
>>> ...
>>> <module>project-e</module>
>>> </modules>
>>> </project>
>>>
>>> project-parent has no <parent> section... or at least does not
>>> reference project-complete
>>>
>>> project-a, project-b, ..., project-e have the following
>>>
>>> <project>
>>> <parent>
>>> <artifactId>project-parent</artifactId>
>>> </parent>
>>> <artifactId>project-___</artifactId>
>>> </project>
>>>
>>>
>>>
>>>
>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>>
>>>> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>>>>>
>>>>> Stephen Connolly wrote:
>>>>>>
>>>>>> sorry i'll correct that...
>>>>>>
>>>>>> you might also want to separate aggregation from inheritance and have
>>>>>> the aggregator pom depend on the child poms, thereby ensuring that the
>>>>>> build plan is correct.
>>>>>
>>>>> Yeah, I'm feeling that... my plan now is to have the modules, say:
>>>>>
>>>>> project-a
>>>>> project-b
>>>>> project-c
>>>>> project-d
>>>>> project-e
>>>>>
>>>>> with module/parent relationship with
>>>>
>>>> I would make project-complete the project with the <modules> section
>>>> and add project-master as a child of project-complete
>>>>
>>>>> project-master
>>>>>
>>>>> and then aggregate in
>>>>>
>>>>> project-complete
>>>>>
>>>>> So then, the dependencies of project-complete would be
>>>>> project-{a,b,c,d,e,},
>>>>> the modules of project-master would be the same, and
>>>>> project-{a,b,c,d,e,complete} would declare project-master as their
>>>>> parent.
>>>>> That make sense?
>>>>>
>>>>> Sam
>>>>>
>>>>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>>>>>
>>>>>>> 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 <dh...@gmail.com>:
>>>>>>>>
>>>>>>>> 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 <
>>>>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>
>>>>> --
>>>>> Sam Barnett-Cormack
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>>
>> --
>> Sam Barnett-Cormack
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
Stephen Connolly wrote:
> my understanding of aggregate is that it has to go where the <modules>
> (& by implication the dependencies) are
Ah, I see! I got the separation slightly wrong. I've got you now, that's
great. So everything is a module of complete, and a dependency of it,
but a-e declare parent to be their parent. Good.
> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>> Ah. Exactly what I meant, but with the names complete and parent the other
>> way around. With the names your way around, the source and javadoc
>> aggregators would go in where?
>>
>> Stephen Connolly wrote:
>>> so to summarize:
>>>
>>> /project-complete
>>> +- project-parent
>>> +- project-a
>>> +- project-b
>>> ...
>>> \- project-e
>>>
>>> project-complete has the following
>>>
>>> <project>
>>> <parent>
>>> <artifactId>project-parent</artifactId>
>>> </parent>
>>> <artifactId>project-___</artifactId>
>>> <modules>
>>> <module>project-parent</module>
>>> <module>project-a</module>
>>> <module>project-b</module>
>>> ...
>>> <module>project-e</module>
>>> </modules>
>>> </project>
>>>
>>> project-parent has no <parent> section... or at least does not
>>> reference project-complete
>>>
>>> project-a, project-b, ..., project-e have the following
>>>
>>> <project>
>>> <parent>
>>> <artifactId>project-parent</artifactId>
>>> </parent>
>>> <artifactId>project-___</artifactId>
>>> </project>
>>>
>>>
>>>
>>>
>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>>>>> Stephen Connolly wrote:
>>>>>> sorry i'll correct that...
>>>>>>
>>>>>> you might also want to separate aggregation from inheritance and have
>>>>>> the aggregator pom depend on the child poms, thereby ensuring that the
>>>>>> build plan is correct.
>>>>> Yeah, I'm feeling that... my plan now is to have the modules, say:
>>>>>
>>>>> project-a
>>>>> project-b
>>>>> project-c
>>>>> project-d
>>>>> project-e
>>>>>
>>>>> with module/parent relationship with
>>>> I would make project-complete the project with the <modules> section
>>>> and add project-master as a child of project-complete
>>>>
>>>>> project-master
>>>>>
>>>>> and then aggregate in
>>>>>
>>>>> project-complete
>>>>>
>>>>> So then, the dependencies of project-complete would be
>>>>> project-{a,b,c,d,e,},
>>>>> the modules of project-master would be the same, and
>>>>> project-{a,b,c,d,e,complete} would declare project-master as their
>>>>> parent.
>>>>> That make sense?
>>>>>
>>>>> Sam
>>>>>
>>>>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>>>>> 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 <dh...@gmail.com>:
>>>>>>>> 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 <
>>>>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>> --
>>>>> Sam Barnett-Cormack
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> --
>> Sam Barnett-Cormack
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Stephen Connolly <st...@gmail.com>.
my understanding of aggregate is that it has to go where the <modules>
(& by implication the dependencies) are
2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
> Ah. Exactly what I meant, but with the names complete and parent the other
> way around. With the names your way around, the source and javadoc
> aggregators would go in where?
>
> Stephen Connolly wrote:
>>
>> so to summarize:
>>
>> /project-complete
>> +- project-parent
>> +- project-a
>> +- project-b
>> ...
>> \- project-e
>>
>> project-complete has the following
>>
>> <project>
>> <parent>
>> <artifactId>project-parent</artifactId>
>> </parent>
>> <artifactId>project-___</artifactId>
>> <modules>
>> <module>project-parent</module>
>> <module>project-a</module>
>> <module>project-b</module>
>> ...
>> <module>project-e</module>
>> </modules>
>> </project>
>>
>> project-parent has no <parent> section... or at least does not
>> reference project-complete
>>
>> project-a, project-b, ..., project-e have the following
>>
>> <project>
>> <parent>
>> <artifactId>project-parent</artifactId>
>> </parent>
>> <artifactId>project-___</artifactId>
>> </project>
>>
>>
>>
>>
>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>
>>> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>>>>
>>>> Stephen Connolly wrote:
>>>>>
>>>>> sorry i'll correct that...
>>>>>
>>>>> you might also want to separate aggregation from inheritance and have
>>>>> the aggregator pom depend on the child poms, thereby ensuring that the
>>>>> build plan is correct.
>>>>
>>>> Yeah, I'm feeling that... my plan now is to have the modules, say:
>>>>
>>>> project-a
>>>> project-b
>>>> project-c
>>>> project-d
>>>> project-e
>>>>
>>>> with module/parent relationship with
>>>
>>> I would make project-complete the project with the <modules> section
>>> and add project-master as a child of project-complete
>>>
>>>> project-master
>>>>
>>>> and then aggregate in
>>>>
>>>> project-complete
>>>>
>>>> So then, the dependencies of project-complete would be
>>>> project-{a,b,c,d,e,},
>>>> the modules of project-master would be the same, and
>>>> project-{a,b,c,d,e,complete} would declare project-master as their
>>>> parent.
>>>> That make sense?
>>>>
>>>> Sam
>>>>
>>>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>>>>
>>>>>> 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 <dh...@gmail.com>:
>>>>>>>
>>>>>>> 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 <
>>>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>
>>>> --
>>>> Sam Barnett-Cormack
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> --
> Sam Barnett-Cormack
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
Ah. Exactly what I meant, but with the names complete and parent the
other way around. With the names your way around, the source and javadoc
aggregators would go in where?
Stephen Connolly wrote:
> so to summarize:
>
> /project-complete
> +- project-parent
> +- project-a
> +- project-b
> ...
> \- project-e
>
> project-complete has the following
>
> <project>
> <parent>
> <artifactId>project-parent</artifactId>
> </parent>
> <artifactId>project-___</artifactId>
> <modules>
> <module>project-parent</module>
> <module>project-a</module>
> <module>project-b</module>
> ...
> <module>project-e</module>
> </modules>
> </project>
>
> project-parent has no <parent> section... or at least does not
> reference project-complete
>
> project-a, project-b, ..., project-e have the following
>
> <project>
> <parent>
> <artifactId>project-parent</artifactId>
> </parent>
> <artifactId>project-___</artifactId>
> </project>
>
>
>
>
> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>>> Stephen Connolly wrote:
>>>> sorry i'll correct that...
>>>>
>>>> you might also want to separate aggregation from inheritance and have
>>>> the aggregator pom depend on the child poms, thereby ensuring that the
>>>> build plan is correct.
>>> Yeah, I'm feeling that... my plan now is to have the modules, say:
>>>
>>> project-a
>>> project-b
>>> project-c
>>> project-d
>>> project-e
>>>
>>> with module/parent relationship with
>> I would make project-complete the project with the <modules> section
>> and add project-master as a child of project-complete
>>
>>> project-master
>>>
>>> and then aggregate in
>>>
>>> project-complete
>>>
>>> So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
>>> the modules of project-master would be the same, and
>>> project-{a,b,c,d,e,complete} would declare project-master as their parent.
>>> That make sense?
>>>
>>> Sam
>>>
>>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>>> 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 <dh...@gmail.com>:
>>>>>> 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 <
>>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>
>>> --
>>> Sam Barnett-Cormack
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Stephen Connolly <st...@gmail.com>.
so to summarize:
/project-complete
+- project-parent
+- project-a
+- project-b
...
\- project-e
project-complete has the following
<project>
<parent>
<artifactId>project-parent</artifactId>
</parent>
<artifactId>project-___</artifactId>
<modules>
<module>project-parent</module>
<module>project-a</module>
<module>project-b</module>
...
<module>project-e</module>
</modules>
</project>
project-parent has no <parent> section... or at least does not
reference project-complete
project-a, project-b, ..., project-e have the following
<project>
<parent>
<artifactId>project-parent</artifactId>
</parent>
<artifactId>project-___</artifactId>
</project>
2009/8/14 Stephen Connolly <st...@gmail.com>:
> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>> Stephen Connolly wrote:
>>>
>>> sorry i'll correct that...
>>>
>>> you might also want to separate aggregation from inheritance and have
>>> the aggregator pom depend on the child poms, thereby ensuring that the
>>> build plan is correct.
>>
>> Yeah, I'm feeling that... my plan now is to have the modules, say:
>>
>> project-a
>> project-b
>> project-c
>> project-d
>> project-e
>>
>> with module/parent relationship with
>
> I would make project-complete the project with the <modules> section
> and add project-master as a child of project-complete
>
>>
>> project-master
>>
>> and then aggregate in
>>
>> project-complete
>>
>> So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
>> the modules of project-master would be the same, and
>> project-{a,b,c,d,e,complete} would declare project-master as their parent.
>> That make sense?
>>
>> Sam
>>
>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>>
>>>> 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 <dh...@gmail.com>:
>>>>>
>>>>> 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 <
>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>>
>> --
>> Sam Barnett-Cormack
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Stephen Connolly <st...@gmail.com>.
SEPARATE aggregation FROM inheritance... otherwise you will get cyclic
2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
> So the one doing the aggregating would have the modules section *and* have
> the dependencies? When I've done that and set the parent in each module,
> it's complained of cyclic dependencies.
>
> Stephen Connolly wrote:
>>
>> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>>>
>>> Stephen Connolly wrote:
>>>>
>>>> sorry i'll correct that...
>>>>
>>>> you might also want to separate aggregation from inheritance and have
>>>> the aggregator pom depend on the child poms, thereby ensuring that the
>>>> build plan is correct.
>>>
>>> Yeah, I'm feeling that... my plan now is to have the modules, say:
>>>
>>> project-a
>>> project-b
>>> project-c
>>> project-d
>>> project-e
>>>
>>> with module/parent relationship with
>>
>> I would make project-complete the project with the <modules> section
>> and add project-master as a child of project-complete
>>
>>> project-master
>>>
>>> and then aggregate in
>>>
>>> project-complete
>>>
>>> So then, the dependencies of project-complete would be
>>> project-{a,b,c,d,e,},
>>> the modules of project-master would be the same, and
>>> project-{a,b,c,d,e,complete} would declare project-master as their
>>> parent.
>>> That make sense?
>>>
>>> Sam
>>>
>>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>>>
>>>>> 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 <dh...@gmail.com>:
>>>>>>
>>>>>> 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 <
>>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>
>>> --
>>> Sam Barnett-Cormack
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> --
> Sam Barnett-Cormack
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
So the one doing the aggregating would have the modules section *and*
have the dependencies? When I've done that and set the parent in each
module, it's complained of cyclic dependencies.
Stephen Connolly wrote:
> 2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
>> Stephen Connolly wrote:
>>> sorry i'll correct that...
>>>
>>> you might also want to separate aggregation from inheritance and have
>>> the aggregator pom depend on the child poms, thereby ensuring that the
>>> build plan is correct.
>> Yeah, I'm feeling that... my plan now is to have the modules, say:
>>
>> project-a
>> project-b
>> project-c
>> project-d
>> project-e
>>
>> with module/parent relationship with
>
> I would make project-complete the project with the <modules> section
> and add project-master as a child of project-complete
>
>> project-master
>>
>> and then aggregate in
>>
>> project-complete
>>
>> So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
>> the modules of project-master would be the same, and
>> project-{a,b,c,d,e,complete} would declare project-master as their parent.
>> That make sense?
>>
>> Sam
>>
>>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>> 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 <dh...@gmail.com>:
>>>>> 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 <
>>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> --
>> Sam Barnett-Cormack
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Stephen Connolly <st...@gmail.com>.
2009/8/14 Sam Barnett-Cormack <s....@lancaster.ac.uk>:
> Stephen Connolly wrote:
>>
>> sorry i'll correct that...
>>
>> you might also want to separate aggregation from inheritance and have
>> the aggregator pom depend on the child poms, thereby ensuring that the
>> build plan is correct.
>
> Yeah, I'm feeling that... my plan now is to have the modules, say:
>
> project-a
> project-b
> project-c
> project-d
> project-e
>
> with module/parent relationship with
I would make project-complete the project with the <modules> section
and add project-master as a child of project-complete
>
> project-master
>
> and then aggregate in
>
> project-complete
>
> So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
> the modules of project-master would be the same, and
> project-{a,b,c,d,e,complete} would declare project-master as their parent.
> That make sense?
>
> Sam
>
>> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>>>
>>> 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 <dh...@gmail.com>:
>>>>
>>>> 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 <
>>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> --
> Sam Barnett-Cormack
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Sam Barnett-Cormack <s....@lancaster.ac.uk>.
Stephen Connolly wrote:
> sorry i'll correct that...
>
> you might also want to separate aggregation from inheritance and have
> the aggregator pom depend on the child poms, thereby ensuring that the
> build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be
project-{a,b,c,d,e,}, the modules of project-master would be the same,
and project-{a,b,c,d,e,complete} would declare project-master as their
parent. That make sense?
Sam
> 2009/8/14 Stephen Connolly <st...@gmail.com>:
>> 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 <dh...@gmail.com>:
>>> 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 <
>>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Sam Barnett-Cormack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Stephen Connolly <st...@gmail.com>.
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 Stephen Connolly <st...@gmail.com>:
> 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 <dh...@gmail.com>:
>> 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 <
>> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by Stephen Connolly <st...@gmail.com>.
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 <dh...@gmail.com>:
> 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 <
> s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: javadoc plugin aggregation woes
Posted by David Hoffer <dh...@gmail.com>.
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 <
s.barnett-cormack@lancaster.ac.uk> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>