You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Martin Hoeller <ma...@xss.co.at> on 2014/03/28 10:36:57 UTC
OutOfMemoryError with maven-javadoc-plugin
Hi!
I have a quite large multimodule project with >150 modules. When
executing "mvn site" the maven-javadoc-plugin is executed with default
configuration. After some time of execution it fails in "aggregate" goal
and I get a
Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded"
I know, I can adjust MAVEN_OPTS to give it more memory and I tried it with
MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" and with
MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m". Both just leading
to another OutOfMemoryError (but no GC overhead limit exceeded).
I'm currently using maven 3.1.1 and tested with m-javadoc-p 2.8 and 2.9.1
(no difference).
So my question is: does any body have some idea how to tweak parameters
to solve this issue?
My current workaround is to disable aggregation in <reporting> section as
described here [0]. But this is really just a workaround, no solution :(
thx for your help,
- martin
[0] https://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-javadocs-report.html
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 28/03/2014 5:29 PM, Martin Hoeller wrote:
> Hi Ron!
>
> On 28 Mär 2014, Ron Wheeler wrote:
>
>> Have you tried increasing the JVM memory past
>>
>> MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m"
>> MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m"
>>
>> You could try something extreme (-Xmx8g ) and see if that changes anything.
> Well, I should have added, that it was working fine with "-Xmx1024m
> -Xms256m -XX:MaxPermSize=512m" recently. Since then I did a minor
> restructure of the project and updated maven from 2.2.1 to 3.1.1. So I
> thought the required memory wouldn't be much more.
Try with Maven 2.1.1 and see if it works.
If it does then the focus shifts to Maven changes.
If it does not then the problem is in what you changed in the project.
"Ron's Basic principle of debugging: Cut problems in half until the
answer falls out."
At least now we know that the problem is caused by a memory leak and
likely caused by something that makes Maven loop which creates objects
that can't be garbage collected.
>
>> -Xms512m is not very useful in this case and you can omit it or make it the same as -XMXnnn.
>> Make sure that you allow enough(???) space after you allocate MaxPermSize.
>>
>> MAVEN_OPTS="-Xmx8g -XX:MaxPermSize=768m"
>>
>>
>> Did you notice that it took longer to run out of memory with the higher
>> settings?
>> If not, then I may be barking up the wrong tree and you might have to
>> change JAVA_OPTS to affect the memory allocation.
>> If it did, then you are heading in the right direction but have not gone
>> far enough yet.
> I tried with 8GB and now it was running for more that 4 hours. Than I
> canceld it because the machine was only swapping and progress was very
> low. (There were only 8GB physical RAM available on the system.)
>
> With 4GB I got the usual OOM error. Can't say if it ran longer. If it
> did, it wasn't that much longer. About 15min or so.
>
> The point is: with maven 2.2.1, m-javadoc-p 2.8 and only minor changes in
> the project layout it was running fine with 1GB. Now it needs at least
> more than 4GB. There must be something wrong.
>
> Any more ideas?
>
> - martin
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Martin Hoeller <ma...@xss.co.at>.
Hi Ron!
On 28 Mär 2014, Ron Wheeler wrote:
> Have you tried increasing the JVM memory past
>
> MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m"
> MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m"
>
> You could try something extreme (-Xmx8g ) and see if that changes anything.
Well, I should have added, that it was working fine with "-Xmx1024m
-Xms256m -XX:MaxPermSize=512m" recently. Since then I did a minor
restructure of the project and updated maven from 2.2.1 to 3.1.1. So I
thought the required memory wouldn't be much more.
> -Xms512m is not very useful in this case and you can omit it or make it the same as -XMXnnn.
> Make sure that you allow enough(???) space after you allocate MaxPermSize.
>
> MAVEN_OPTS="-Xmx8g -XX:MaxPermSize=768m"
>
>
> Did you notice that it took longer to run out of memory with the higher
> settings?
> If not, then I may be barking up the wrong tree and you might have to
> change JAVA_OPTS to affect the memory allocation.
> If it did, then you are heading in the right direction but have not gone
> far enough yet.
I tried with 8GB and now it was running for more that 4 hours. Than I
canceld it because the machine was only swapping and progress was very
low. (There were only 8GB physical RAM available on the system.)
With 4GB I got the usual OOM error. Can't say if it ran longer. If it
did, it wasn't that much longer. About 15min or so.
The point is: with maven 2.2.1, m-javadoc-p 2.8 and only minor changes in
the project layout it was running fine with 1GB. Now it needs at least
more than 4GB. There must be something wrong.
Any more ideas?
- martin
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Ron Wheeler <rw...@artifact-software.com>.
Have you tried increasing the JVM memory past
MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m"
MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m"
You could try something extreme (-Xmx8g ) and see if that changes anything.
-Xms512m is not very useful in this case and you can omit it or make it the same as -XMXnnn.
Make sure that you allow enough(???) space after you allocate MaxPermSize.
MAVEN_OPTS="-Xmx8g -XX:MaxPermSize=768m"
Did you notice that it took longer to run out of memory with the higher
settings?
If not, then I may be barking up the wrong tree and you might have to
change JAVA_OPTS to affect the memory allocation.
If it did, then you are heading in the right direction but have not gone
far enough yet.
Ron
On 28/03/2014 7:24 AM, Martin Hoeller wrote:
> Hi Baptiste!
>
> I tried it but it didn't change anything. Still OutOfMemoryError :(
>
> -martin
>
> On 28 Mär 2014, Baptiste Mathus wrote:
>
>> Sorry, I haven't used javadoc for years now, but as javadoc is an external
>> tool, I guess you should specify additionalJOption?
>> http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#additionalJOption
>>
>> Cheers
>>
>>
>> 2014-03-28 10:36 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
>>
>>> Hi!
>>>
>>> I have a quite large multimodule project with >150 modules. When
>>> executing "mvn site" the maven-javadoc-plugin is executed with default
>>> configuration. After some time of execution it fails in "aggregate" goal
>>> and I get a
>>>
>>> Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit
>>> exceeded"
>>>
>>> I know, I can adjust MAVEN_OPTS to give it more memory and I tried it with
>>> MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" and with
>>> MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m". Both just leading
>>> to another OutOfMemoryError (but no GC overhead limit exceeded).
>>>
>>> I'm currently using maven 3.1.1 and tested with m-javadoc-p 2.8 and 2.9.1
>>> (no difference).
>>>
>>> So my question is: does any body have some idea how to tweak parameters
>>> to solve this issue?
>>>
>>> My current workaround is to disable aggregation in <reporting> section as
>>> described here [0]. But this is really just a workaround, no solution :(
>>>
>>> thx for your help,
>>> - martin
>>>
>>> [0]
>>> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-javadocs-report.html
>>>
>>
>>
>> --
>> Baptiste <Batmat> MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Robert Scholte <rf...@apache.org>.
Hi,
See also
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#debug
With the generated script you can experiment without the overhead of Maven.
Robert
Op Fri, 28 Mar 2014 22:31:12 +0100 schreef Martin Hoeller
<ma...@xss.co.at>:
> On 28 Mär 2014, Justin Georgeson wrote:
>
>> The maven-javadoc-plugin has a maxmemory configuration parameter. In my
>> parent POM I set a default property docs.maxMemory and then configure
>> maven-javadoc-plugin with
>>
>> <maxmemory>${docs.maxMemory}</maxmemory>
>>
>> So each team can override that default setting in their pom.xml if they
>> have an unusually large codebase, or set it really high on the command
>> line for an aggregate javadoc of the entire multi-project workspace.
>
> I already experimented with the maxmemory option without success. I'll
> try some more in combination with the other memory options.
>
> thx,
> - martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Martin Hoeller <ma...@xss.co.at>.
On 28 Mär 2014, Justin Georgeson wrote:
> The maven-javadoc-plugin has a maxmemory configuration parameter. In my parent POM I set a default property docs.maxMemory and then configure maven-javadoc-plugin with
>
> <maxmemory>${docs.maxMemory}</maxmemory>
>
> So each team can override that default setting in their pom.xml if they have an unusually large codebase, or set it really high on the command line for an aggregate javadoc of the entire multi-project workspace.
I already experimented with the maxmemory option without success. I'll
try some more in combination with the other memory options.
thx,
- martin
RE: OutOfMemoryError with maven-javadoc-plugin
Posted by Justin Georgeson <JG...@lgc.com>.
The maven-javadoc-plugin has a maxmemory configuration parameter. In my parent POM I set a default property docs.maxMemory and then configure maven-javadoc-plugin with
<maxmemory>${docs.maxMemory}</maxmemory>
So each team can override that default setting in their pom.xml if they have an unusually large codebase, or set it really high on the command line for an aggregate javadoc of the entire multi-project workspace.
-----Original Message-----
From: Martin Hoeller [mailto:martin@xss.co.at]
Sent: Friday, March 28, 2014 8:39 AM
To: Baptiste Mathus
Cc: Maven Users List
Subject: Re: OutOfMemoryError with maven-javadoc-plugin
Yes I did. If I tried without "-J" I got some error.
On 28 Mär 2014, Baptiste Mathus wrote:
> Did you make sure you put -J-Xmx and not only -Xmx ?
>
>
> 2014-03-28 12:24 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
>
> > Hi Baptiste!
> >
> > I tried it but it didn't change anything. Still OutOfMemoryError :(
> >
> > -martin
> >
> > On 28 Mär 2014, Baptiste Mathus wrote:
> >
> > > Sorry, I haven't used javadoc for years now, but as javadoc is an
> > external
> > > tool, I guess you should specify additionalJOption?
> > >
> > http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.ht
> > ml#additionalJOption
> > >
> > > Cheers
> > >
> > >
> > > 2014-03-28 10:36 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
> > >
> > > > Hi!
> > > >
> > > > I have a quite large multimodule project with >150 modules. When
> > > > executing "mvn site" the maven-javadoc-plugin is executed with
> > > > default configuration. After some time of execution it fails in "aggregate"
> > goal
> > > > and I get a
> > > >
> > > > Exception in thread "main" java.lang.OutOfMemoryError: GC
> > > > overhead
> > limit
> > > > exceeded"
> > > >
> > > > I know, I can adjust MAVEN_OPTS to give it more memory and I
> > > > tried it
> > with
> > > > MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" and with
> > > > MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m". Both just
> > > > leading to another OutOfMemoryError (but no GC overhead limit exceeded).
> > > >
> > > > I'm currently using maven 3.1.1 and tested with m-javadoc-p 2.8
> > > > and
> > 2.9.1
> > > > (no difference).
> > > >
> > > > So my question is: does any body have some idea how to tweak
> > > > parameters to solve this issue?
> > > >
> > > > My current workaround is to disable aggregation in <reporting>
> > > > section
> > as
> > > > described here [0]. But this is really just a workaround, no
> > > > solution
> > :(
> > > >
> > > > thx for your help,
> > > > - martin
> > > >
> > > > [0]
> > > >
> > https://maven.apache.org/plugins/maven-javadoc-plugin/examples/selec
> > tive-javadocs-report.html
> > > >
> > >
> > >
> > >
> > > --
> > > Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre,
> > > Mangez un castor !
> >
> >
> > --
> > Martin Höller | martin.hoeller@xss.co.at
> > *x Software + Systeme | http://www.xss.co.at/
> > Karmarschgasse 51/2/20 | Tel: +43-1-6060114-40
> > A-1100 Vienna, Austria | Fax: +43-1-6060114-71
> >
>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez
> un castor !
--
Martin Höller | martin.hoeller@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-40
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Martin Hoeller <ma...@xss.co.at>.
Yes I did. If I tried without "-J" I got some error.
On 28 Mär 2014, Baptiste Mathus wrote:
> Did you make sure you put -J-Xmx and not only -Xmx ?
>
>
> 2014-03-28 12:24 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
>
> > Hi Baptiste!
> >
> > I tried it but it didn't change anything. Still OutOfMemoryError :(
> >
> > -martin
> >
> > On 28 Mär 2014, Baptiste Mathus wrote:
> >
> > > Sorry, I haven't used javadoc for years now, but as javadoc is an
> > external
> > > tool, I guess you should specify additionalJOption?
> > >
> > http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#additionalJOption
> > >
> > > Cheers
> > >
> > >
> > > 2014-03-28 10:36 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
> > >
> > > > Hi!
> > > >
> > > > I have a quite large multimodule project with >150 modules. When
> > > > executing "mvn site" the maven-javadoc-plugin is executed with default
> > > > configuration. After some time of execution it fails in "aggregate"
> > goal
> > > > and I get a
> > > >
> > > > Exception in thread "main" java.lang.OutOfMemoryError: GC overhead
> > limit
> > > > exceeded"
> > > >
> > > > I know, I can adjust MAVEN_OPTS to give it more memory and I tried it
> > with
> > > > MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" and with
> > > > MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m". Both just leading
> > > > to another OutOfMemoryError (but no GC overhead limit exceeded).
> > > >
> > > > I'm currently using maven 3.1.1 and tested with m-javadoc-p 2.8 and
> > 2.9.1
> > > > (no difference).
> > > >
> > > > So my question is: does any body have some idea how to tweak parameters
> > > > to solve this issue?
> > > >
> > > > My current workaround is to disable aggregation in <reporting> section
> > as
> > > > described here [0]. But this is really just a workaround, no solution
> > :(
> > > >
> > > > thx for your help,
> > > > - martin
> > > >
> > > > [0]
> > > >
> > https://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-javadocs-report.html
> > > >
> > >
> > >
> > >
> > > --
> > > Baptiste <Batmat> MATHUS - http://batmat.net
> > > Sauvez un arbre,
> > > Mangez un castor !
> >
> >
> > --
> > Martin Höller | martin.hoeller@xss.co.at
> > *x Software + Systeme | http://www.xss.co.at/
> > Karmarschgasse 51/2/20 | Tel: +43-1-6060114-40
> > A-1100 Vienna, Austria | Fax: +43-1-6060114-71
> >
>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
--
Martin Höller | martin.hoeller@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-40
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Baptiste Mathus <bm...@batmat.net>.
Did you make sure you put -J-Xmx and not only -Xmx ?
2014-03-28 12:24 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
> Hi Baptiste!
>
> I tried it but it didn't change anything. Still OutOfMemoryError :(
>
> -martin
>
> On 28 Mär 2014, Baptiste Mathus wrote:
>
> > Sorry, I haven't used javadoc for years now, but as javadoc is an
> external
> > tool, I guess you should specify additionalJOption?
> >
> http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#additionalJOption
> >
> > Cheers
> >
> >
> > 2014-03-28 10:36 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
> >
> > > Hi!
> > >
> > > I have a quite large multimodule project with >150 modules. When
> > > executing "mvn site" the maven-javadoc-plugin is executed with default
> > > configuration. After some time of execution it fails in "aggregate"
> goal
> > > and I get a
> > >
> > > Exception in thread "main" java.lang.OutOfMemoryError: GC overhead
> limit
> > > exceeded"
> > >
> > > I know, I can adjust MAVEN_OPTS to give it more memory and I tried it
> with
> > > MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" and with
> > > MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m". Both just leading
> > > to another OutOfMemoryError (but no GC overhead limit exceeded).
> > >
> > > I'm currently using maven 3.1.1 and tested with m-javadoc-p 2.8 and
> 2.9.1
> > > (no difference).
> > >
> > > So my question is: does any body have some idea how to tweak parameters
> > > to solve this issue?
> > >
> > > My current workaround is to disable aggregation in <reporting> section
> as
> > > described here [0]. But this is really just a workaround, no solution
> :(
> > >
> > > thx for your help,
> > > - martin
> > >
> > > [0]
> > >
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-javadocs-report.html
> > >
> >
> >
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
>
>
> --
> Martin Höller | martin.hoeller@xss.co.at
> *x Software + Systeme | http://www.xss.co.at/
> Karmarschgasse 51/2/20 | Tel: +43-1-6060114-40
> A-1100 Vienna, Austria | Fax: +43-1-6060114-71
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Martin Hoeller <ma...@xss.co.at>.
Hi Baptiste!
I tried it but it didn't change anything. Still OutOfMemoryError :(
-martin
On 28 Mär 2014, Baptiste Mathus wrote:
> Sorry, I haven't used javadoc for years now, but as javadoc is an external
> tool, I guess you should specify additionalJOption?
> http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#additionalJOption
>
> Cheers
>
>
> 2014-03-28 10:36 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
>
> > Hi!
> >
> > I have a quite large multimodule project with >150 modules. When
> > executing "mvn site" the maven-javadoc-plugin is executed with default
> > configuration. After some time of execution it fails in "aggregate" goal
> > and I get a
> >
> > Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit
> > exceeded"
> >
> > I know, I can adjust MAVEN_OPTS to give it more memory and I tried it with
> > MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" and with
> > MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m". Both just leading
> > to another OutOfMemoryError (but no GC overhead limit exceeded).
> >
> > I'm currently using maven 3.1.1 and tested with m-javadoc-p 2.8 and 2.9.1
> > (no difference).
> >
> > So my question is: does any body have some idea how to tweak parameters
> > to solve this issue?
> >
> > My current workaround is to disable aggregation in <reporting> section as
> > described here [0]. But this is really just a workaround, no solution :(
> >
> > thx for your help,
> > - martin
> >
> > [0]
> > https://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-javadocs-report.html
> >
>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
--
Martin Höller | martin.hoeller@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-40
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
Re: OutOfMemoryError with maven-javadoc-plugin
Posted by Baptiste Mathus <bm...@batmat.net>.
Sorry, I haven't used javadoc for years now, but as javadoc is an external
tool, I guess you should specify additionalJOption?
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#additionalJOption
Cheers
2014-03-28 10:36 GMT+01:00 Martin Hoeller <ma...@xss.co.at>:
> Hi!
>
> I have a quite large multimodule project with >150 modules. When
> executing "mvn site" the maven-javadoc-plugin is executed with default
> configuration. After some time of execution it fails in "aggregate" goal
> and I get a
>
> Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit
> exceeded"
>
> I know, I can adjust MAVEN_OPTS to give it more memory and I tried it with
> MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" and with
> MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m". Both just leading
> to another OutOfMemoryError (but no GC overhead limit exceeded).
>
> I'm currently using maven 3.1.1 and tested with m-javadoc-p 2.8 and 2.9.1
> (no difference).
>
> So my question is: does any body have some idea how to tweak parameters
> to solve this issue?
>
> My current workaround is to disable aggregation in <reporting> section as
> described here [0]. But this is really just a workaround, no solution :(
>
> thx for your help,
> - martin
>
> [0]
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-javadocs-report.html
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !