[ http://jira.codehaus.org/browse/MJAVADOC-102?page=all ]
Vincent Siveton closed MJAVADOC-102.
------------------------------------
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.1
Already fixed
> Error in multimodule project gives very misleading error messages
> -----------------------------------------------------------------
>
> Key: MJAVADOC-102
> URL: http://jira.codehaus.org/browse/MJAVADOC-102
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Windows XP
> Sun Java 1.5.0_07
> Reporter: Adam Lally
> Assigned To: Vincent Siveton
> Priority: Minor
> Fix For: 2.1
>
> Attachments: maven-javadoc-bug.zip
>
>
> The attached zip has a multimodule project with 2 modules. module 2 has an
> invalid package.html file.
> In the parent directory, run "mvn install". This should work fine.
> Then run "mvn javadoc:javadoc". When I do this, I get:
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] An error has occurred in JavaDocs report generation.
> Embedded error: Exit code: 1 -
> C:/alally/dev/maven-javadoc-bug/module1/src/main/java/test/module1/Test.java:3:
> package org.eclipse.emf.common.util does not exist
> import org.eclipse.emf.common.util.EList;
> ^
> C:/alally/dev/maven-javadoc-bug/module1/src/main/java/test/module1/Test.java:6:
> cannot find symbol
> symbol : class EList
> location: class test.module1.Test
> public static void foo(EList bar) {}
> ^
> C:\alally\dev\maven-javadoc-bug\module2\src\main\java\test\module2\package.html:
> error - Body tag missing from HTML
> -------------------------------------------------------------------
> In addition to the correct error message about the missing body tag, you can
> see I'm also getting a bogus "cannot find symbol" error.
> In my real project, I was getting *hundreds* of "cannot find symbol" errors,
> making it very difficult to see what the real problem is. This caused me to
> waste a few hours trying to figure out why my dependencies weren't being
> resolved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
