Impossible to aggregate javadoc if snapshot never built

The same problem appears during the use of the release plugin: the release fails and I have to install the checked-out code locally before retrying the release.

I face the same problem. It seems to be a regression, as the problem does not occur with maven-javadoc-plugin 2.0.

Same thing with releases version of artifacts.

This is a major issue in a multi-module project when you want to release the project and the aggregated javadoc.

As the maven-release-plugin does "deploy site-deploy" when release:perform, this step always fails because of this bug.

Attached a small test case.
I noticed that the bug is triggered if a module depends on another, even if in correct order.
This bug is still present in the 2.3 version of the plugin.

Could someone add the "Testcase included" flag?
Thanks.

testcase included flag to yes.

Fixed in r617996.
Snapshot deployed but you need to have maven 2.0.8 to run it.

I tried with Maven 2.0.8 and maven-javadoc-plugin-2.4-20080203.152011-3

[INFO] Generate "JavaDocs" report.
[INFO] snapshot tele.persistance:pers-commons:jar:1.3.0-M1-SNAPSHOT: checking for updates from apache.snapshots
Downloading: http://people.apache.org/maven-snapshot-repository/tele/persistance/pers-commons/1.3.0-M1-SNAPSHOT/pers-commons-1.3.0-M1-SNAPSHOT.jar
[WARNING] The dependency: [tele.persistance:pers-commons:jar:1.3.0-M1-SNAPSHOT} can't be resolved but has been found in the reactor (probably snapshots).
This dependency has been excluded from the Javadoc classpath. You should rerun javadoc after executing mvn install.
[WARNING] IGNORED to add some artifacts in the classpath. See above.

...

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error during page generation

Embedded error: Error rendering Maven report: Missing:
----------
1) tele.persistance:pers-test:jar:tests:1.3.0-M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
      mvn install:install-file -DgroupId=tele.persistance -DartifactId=pers-test -Dversion=1.3.0-M1-SNAPSHOT -Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file

...

I don't know if javadoc is correctly generated when I see all those WARNING messages.
Then build fails because of a dependency with "tests" classifier.

2 questions :

• when a jar file located in reactor is excluded from javadoc, are corresponding project's classes still included in javadoc ? (aggregate = true)

• are classifiers handled by reactor jar exclusion ?

Reopen since checkMissingArtifactsInReactor() doesnt take care of classifier.

Damien, did you call mvn site or mvn javadoc:javadoc?
Could you send us a log with -X?

> did you call mvn site or mvn javadoc:javadoc?

mvn -DreleaseProfile=true clean deploy site-deploy

So both site and javadoc:javadoc together.

Log file is coming...

Log file for mvn -X -DreleaseProfile=true clean deploy site-deploy in attachement.

Good luck

Vincent, do you need more information to fix the problem ?

"mvn -DreleaseProfile=true clean deploy site-deploy" works for me with the latest maven-javadoc-plugin snapshot and the attached example.

(Well, after adding <distributionManagement> – for future examples, you can use something like file:///tmp/repo-MJAVADOC-116 as the deployment repo url, and likewise for the site deployment url.)

I'm not sure of the timing, but this may have been fixed by along with MJAVADOC-137 by reverting the change from MJAVADOC-104 that added @aggregator.

Still doesn't work with classifiers

Damien, it seems that it is due to @requiresDependencyResolution, not the Javadoc plugin.
Could you confirm that the error comes from DefaultPluginManager ?

As mentioned, I can't reproduce this with the attached example.

I'd like to stage the 2.4 release on Friday.

In order for this to be included, I need a sample project and steps to reproduce the problem. Otherwise it will either be bumped to 2.5 or closed as Cannot Reproduce. Thanks!

Wendy, can you wait one day? I tried some days ago with Tiles and it didn't work.

Here is a test case which reproduces problem with classifiers and aggregated javadoc.

It is based on previous patch with following updates :

• javadoc version 2.4-SNAPSHOT
• build module 1 test jar ("test-jar" classifier)
• module 2 depends on module 1 jar AND test-jar. They have to be declared together.

Try "mvn -DreleaseProfile=true clean deploy site-deploy", it will fail (maven 2.0.8)

Things to notice :

• with aggregate = false, it works
• in module 2, with exactly one of the 2 dependencies (jar OR test-jar), it works (??)

Is it enough to reproduce bug ?

Same test cas as before, but without any target folders.

Creating Javadocs with:
mvn javadoc:javadoc
does not work with Tiles:
http://svn.apache.org/repos/asf/tiles/framework/trunk/

Added tiles-log.txt as attachment.

Antonio, same problem as me with classifiers.

Wendy, this fix is waited for a long time by many people and is really a major issue.
Is it really not possible to work on this for 2.4 ?

This is a real thorn in our sides. Seems like we may have to disable this plugin.

MJAVADOC-197 could be a workaround for this issue.

MJAVADOC-197 is the only workaround that we could propose at this time.

Closed as fixed?
This bug is not fixed, there is only a workaround!
And anyway, we need to publish aggregated javadoc in Tiles when releasing it through the release plugin.
Our workaround is installing the tagged version (tagged using release:prepare) before running release:perform.

So please reopen this bug, or close it as "won't fix", "fixed" is misleading.

As requested

As requested on dev@ by Antonio

This problem still persist with version 2.5. I tried both aggregate configurations and even defined javadoc only at module level but still it tries to download dependent snapshot modules which are not built yet.

Can someone explain what is the workaround?

I think that the workaround in MJAVADOC-197 refers to the failOnError flag:
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#failOnError

It is still failing the build if javadoc is run in aggregate mode. I set the <failOnError>false</failOnError> but it still fails.

Tested on Tiles 2.2.0 snapshot (never published).
Upgrading to Javadoc plugin 2.6 and using the "aggregate" goal, it seems to work even if the snapshot was never built.

The fix might be due to MJAVADOC-181.

This issue could be due to MNG-3685 defect.

Not sure if this is a dupe or just related

We have the same behaviour, as soon as the aggregate goal is called. In our case, this arrives in the default lifecycle, since we attached the javadoc plugin to the verify phase through a profile. When the profile is activated, the build fails. Furthermore, failOnError , as decribed in http://jira.codehaus.org/browse/MJAVADOC-197, has no effect here.

We use maven 3.0.4 and javadoc plugin 2.8.1.

I attach a project which should allow to reproduce the problem.

The problem should be reproducible with the project in mymobiliartest.zip