You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dennis Lundberg <de...@apache.org> on 2011/04/27 20:32:10 UTC
Javadoc Plugin problems during Doxia release
Hi
As I mentioned in the vote thread I had serious problems with the
Javadoc Plugin during the release. After having done some more testing
I'd like to present my findings.
1. The Javadoc Plugin has class loading interference when run from
Maven 2.2.1. Somehow the class path is modified and broken during a
build. In my case this leads to an exception during Javadoc generation.
See stack trace below. This meant that I could not publish the site
using Maven 2.2.1. Using Maven 3.0.3 worked.
Upgrading to the latest 2.8-SNAPSHOT of the plugin does not solve this
issue. I don't know whether the bug is in Maven or the Javadoc Plugin,
but I'm guessing the latter. Looking through the current unresolved
issues fr Javadoc Plugin I'm unable to find a matching issue.
2. Version 2.7 of the Javadoc Plugin takes exponentionally longer time
to run based on the number of modules in a multi module build. Doing
'mvn site:stage-deploy -Preporting' for Doxia took 89 minutes on my new
4-core, 8GB, SSD-equipped machine. No, I'm not kidding - 89 minutes!
Doxia has 19 modules. For each module the Javadocs (and test Javadocs)
for *all* the other modules are created. You do the math.
The good thing is that this seems to have been fixed in 2.8-SNAPSHOT,
probably in MJAVADOC-284. We need to release 2.8 and update maven-parent
to that ASAP.
Stacktrace when running 'mvn site -Preporting' on the current trunk of
Doxia Sitetools. You should be able to use the revision prior to the
release (r1096869) to see this, if you haven't yet downloaded the staged
1.2-version of Doxia. A similar stacktrace occurs for Doxia, but the
build time for that project is considerably longer.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error during page generation
Embedded error: Error rendering Maven report:
Exit code: 1 -
G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\main\java\org\apache\maven\doxia\siterenderer\DefaultSiteRenderer.java:57:
cannot find symbol
symbol : class Doxia
location: package org.apache.maven.doxia
import org.apache.maven.doxia.Doxia;
^
...
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Javadoc Plugin problems during Doxia release
Posted by Robert Scholte <rf...@codehaus.org>.
Dennis,
I noticed similar problems when someone tried to release the cobertura-m-p-2.5.
He rolled back the release, made a jira-issue[1], changed the configuration of the m-javadoc-p[2] and retried the release.
I didn't have time to investigate this yet (this should be fixed in the mojo-parent of course) but I know he's using M2 while I'm using M3.
It might give you a hint.
-Robert
[1] http://jira.codehaus.org/browse/MCOBERTURA-141
[2] https://fisheye.codehaus.org/changelog/mojo/?cs=13909
> Date: Wed, 27 Apr 2011 20:32:10 +0200
> From: dennisl@apache.org
> To: dev@maven.apache.org
> Subject: Javadoc Plugin problems during Doxia release
>
> Hi
>
> As I mentioned in the vote thread I had serious problems with the
> Javadoc Plugin during the release. After having done some more testing
> I'd like to present my findings.
>
>
> 1. The Javadoc Plugin has class loading interference when run from
> Maven 2.2.1. Somehow the class path is modified and broken during a
> build. In my case this leads to an exception during Javadoc generation.
> See stack trace below. This meant that I could not publish the site
> using Maven 2.2.1. Using Maven 3.0.3 worked.
>
> Upgrading to the latest 2.8-SNAPSHOT of the plugin does not solve this
> issue. I don't know whether the bug is in Maven or the Javadoc Plugin,
> but I'm guessing the latter. Looking through the current unresolved
> issues fr Javadoc Plugin I'm unable to find a matching issue.
>
>
> 2. Version 2.7 of the Javadoc Plugin takes exponentionally longer time
> to run based on the number of modules in a multi module build. Doing
> 'mvn site:stage-deploy -Preporting' for Doxia took 89 minutes on my new
> 4-core, 8GB, SSD-equipped machine. No, I'm not kidding - 89 minutes!
>
> Doxia has 19 modules. For each module the Javadocs (and test Javadocs)
> for *all* the other modules are created. You do the math.
>
> The good thing is that this seems to have been fixed in 2.8-SNAPSHOT,
> probably in MJAVADOC-284. We need to release 2.8 and update maven-parent
> to that ASAP.
>
>
>
> Stacktrace when running 'mvn site -Preporting' on the current trunk of
> Doxia Sitetools. You should be able to use the revision prior to the
> release (r1096869) to see this, if you haven't yet downloaded the staged
> 1.2-version of Doxia. A similar stacktrace occurs for Doxia, but the
> build time for that project is considerably longer.
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error during page generation
>
> Embedded error: Error rendering Maven report:
> Exit code: 1 -
> G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\main\java\org\apache\maven\doxia\siterenderer\DefaultSiteRenderer.java:57:
> cannot find symbol
> symbol : class Doxia
> location: package org.apache.maven.doxia
> import org.apache.maven.doxia.Doxia;
> ^
> ...
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Re: Javadoc Plugin problems during Doxia release
Posted by Hervé BOUTEMY <he...@free.fr>.
I tracked down the issue and found that it is caused by MPIR-223
regards,
Hervé
Le jeudi 28 avril 2011, Dennis Lundberg a écrit :
> Hervé BOUTEMY skrev 2011-04-27 23:39:
> > could the first point be the same as MJAVADOC-302?
> > I'll try to have a look.
>
> I looked at that issue and it might be the same problem. There isn't
> much info in that issue though.
>
> > About releasing 2.8, I was hoping to make a release shortly since
> > MJAVADOC-284 is known as really blocking: the question is whether we try
> > to fix other issues before or if I should start the release process ASAP
>
> If the class path problem is in the Javadoc Plugin then we could have a
> go at fixing it in 2.8. Or we could simply do two releases.
>
> > Regards,
> >
> > Hervé
> >
> > Le mercredi 27 avril 2011, Dennis Lundberg a écrit :
> >> Hi
> >>
> >> As I mentioned in the vote thread I had serious problems with the
> >> Javadoc Plugin during the release. After having done some more testing
> >> I'd like to present my findings.
> >>
> >>
> >> 1. The Javadoc Plugin has class loading interference when run from
> >> Maven 2.2.1. Somehow the class path is modified and broken during a
> >> build. In my case this leads to an exception during Javadoc generation.
> >> See stack trace below. This meant that I could not publish the site
> >> using Maven 2.2.1. Using Maven 3.0.3 worked.
> >>
> >> Upgrading to the latest 2.8-SNAPSHOT of the plugin does not solve this
> >> issue. I don't know whether the bug is in Maven or the Javadoc Plugin,
> >> but I'm guessing the latter. Looking through the current unresolved
> >> issues fr Javadoc Plugin I'm unable to find a matching issue.
> >>
> >>
> >> 2. Version 2.7 of the Javadoc Plugin takes exponentionally longer time
> >> to run based on the number of modules in a multi module build. Doing
> >> 'mvn site:stage-deploy -Preporting' for Doxia took 89 minutes on my new
> >> 4-core, 8GB, SSD-equipped machine. No, I'm not kidding - 89 minutes!
> >>
> >> Doxia has 19 modules. For each module the Javadocs (and test Javadocs)
> >> for *all* the other modules are created. You do the math.
> >>
> >> The good thing is that this seems to have been fixed in 2.8-SNAPSHOT,
> >> probably in MJAVADOC-284. We need to release 2.8 and update maven-parent
> >> to that ASAP.
> >>
> >>
> >>
> >> Stacktrace when running 'mvn site -Preporting' on the current trunk of
> >> Doxia Sitetools. You should be able to use the revision prior to the
> >> release (r1096869) to see this, if you haven't yet downloaded the staged
> >> 1.2-version of Doxia. A similar stacktrace occurs for Doxia, but the
> >> build time for that project is considerably longer.
> >>
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Error during page generation
> >>
> >> Embedded error: Error rendering Maven report:
> >> Exit code: 1 -
> >> G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\mai
> >> n\j ava\org\apache\maven\doxia\siterenderer\DefaultSiteRenderer.java:57:
> >> cannot find symbol
> >> symbol : class Doxia
> >> location: package org.apache.maven.doxia
> >> import org.apache.maven.doxia.Doxia;
> >>
> >> ^
> >>
> >> ...
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Javadoc Plugin problems during Doxia release
Posted by Dennis Lundberg <de...@apache.org>.
Hervé BOUTEMY skrev 2011-04-27 23:39:
> could the first point be the same as MJAVADOC-302?
> I'll try to have a look.
I looked at that issue and it might be the same problem. There isn't
much info in that issue though.
>
> About releasing 2.8, I was hoping to make a release shortly since MJAVADOC-284
> is known as really blocking: the question is whether we try to fix other issues
> before or if I should start the release process ASAP
If the class path problem is in the Javadoc Plugin then we could have a
go at fixing it in 2.8. Or we could simply do two releases.
> Regards,
>
> Hervé
>
> Le mercredi 27 avril 2011, Dennis Lundberg a écrit :
>> Hi
>>
>> As I mentioned in the vote thread I had serious problems with the
>> Javadoc Plugin during the release. After having done some more testing
>> I'd like to present my findings.
>>
>>
>> 1. The Javadoc Plugin has class loading interference when run from
>> Maven 2.2.1. Somehow the class path is modified and broken during a
>> build. In my case this leads to an exception during Javadoc generation.
>> See stack trace below. This meant that I could not publish the site
>> using Maven 2.2.1. Using Maven 3.0.3 worked.
>>
>> Upgrading to the latest 2.8-SNAPSHOT of the plugin does not solve this
>> issue. I don't know whether the bug is in Maven or the Javadoc Plugin,
>> but I'm guessing the latter. Looking through the current unresolved
>> issues fr Javadoc Plugin I'm unable to find a matching issue.
>>
>>
>> 2. Version 2.7 of the Javadoc Plugin takes exponentionally longer time
>> to run based on the number of modules in a multi module build. Doing
>> 'mvn site:stage-deploy -Preporting' for Doxia took 89 minutes on my new
>> 4-core, 8GB, SSD-equipped machine. No, I'm not kidding - 89 minutes!
>>
>> Doxia has 19 modules. For each module the Javadocs (and test Javadocs)
>> for *all* the other modules are created. You do the math.
>>
>> The good thing is that this seems to have been fixed in 2.8-SNAPSHOT,
>> probably in MJAVADOC-284. We need to release 2.8 and update maven-parent
>> to that ASAP.
>>
>>
>>
>> Stacktrace when running 'mvn site -Preporting' on the current trunk of
>> Doxia Sitetools. You should be able to use the revision prior to the
>> release (r1096869) to see this, if you haven't yet downloaded the staged
>> 1.2-version of Doxia. A similar stacktrace occurs for Doxia, but the
>> build time for that project is considerably longer.
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error during page generation
>>
>> Embedded error: Error rendering Maven report:
>> Exit code: 1 -
>> G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\main\j
>> ava\org\apache\maven\doxia\siterenderer\DefaultSiteRenderer.java:57: cannot
>> find symbol
>> symbol : class Doxia
>> location: package org.apache.maven.doxia
>> import org.apache.maven.doxia.Doxia;
>> ^
>> ...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Javadoc Plugin problems during Doxia release
Posted by Hervé BOUTEMY <he...@free.fr>.
could the first point be the same as MJAVADOC-302?
I'll try to have a look.
About releasing 2.8, I was hoping to make a release shortly since MJAVADOC-284
is known as really blocking: the question is whether we try to fix other issues
before or if I should start the release process ASAP
Regards,
Hervé
Le mercredi 27 avril 2011, Dennis Lundberg a écrit :
> Hi
>
> As I mentioned in the vote thread I had serious problems with the
> Javadoc Plugin during the release. After having done some more testing
> I'd like to present my findings.
>
>
> 1. The Javadoc Plugin has class loading interference when run from
> Maven 2.2.1. Somehow the class path is modified and broken during a
> build. In my case this leads to an exception during Javadoc generation.
> See stack trace below. This meant that I could not publish the site
> using Maven 2.2.1. Using Maven 3.0.3 worked.
>
> Upgrading to the latest 2.8-SNAPSHOT of the plugin does not solve this
> issue. I don't know whether the bug is in Maven or the Javadoc Plugin,
> but I'm guessing the latter. Looking through the current unresolved
> issues fr Javadoc Plugin I'm unable to find a matching issue.
>
>
> 2. Version 2.7 of the Javadoc Plugin takes exponentionally longer time
> to run based on the number of modules in a multi module build. Doing
> 'mvn site:stage-deploy -Preporting' for Doxia took 89 minutes on my new
> 4-core, 8GB, SSD-equipped machine. No, I'm not kidding - 89 minutes!
>
> Doxia has 19 modules. For each module the Javadocs (and test Javadocs)
> for *all* the other modules are created. You do the math.
>
> The good thing is that this seems to have been fixed in 2.8-SNAPSHOT,
> probably in MJAVADOC-284. We need to release 2.8 and update maven-parent
> to that ASAP.
>
>
>
> Stacktrace when running 'mvn site -Preporting' on the current trunk of
> Doxia Sitetools. You should be able to use the revision prior to the
> release (r1096869) to see this, if you haven't yet downloaded the staged
> 1.2-version of Doxia. A similar stacktrace occurs for Doxia, but the
> build time for that project is considerably longer.
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error during page generation
>
> Embedded error: Error rendering Maven report:
> Exit code: 1 -
> G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\main\j
> ava\org\apache\maven\doxia\siterenderer\DefaultSiteRenderer.java:57: cannot
> find symbol
> symbol : class Doxia
> location: package org.apache.maven.doxia
> import org.apache.maven.doxia.Doxia;
> ^
> ...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org