[ http://jira.codehaus.org/browse/MJAVADOC-103?page=comments#action_80653 ] Adam Lally commented on MJAVADOC-103: -------------------------------------
However, it does not seem to *always* ignore the classpath of the child. I have a multimodule build where most of the modules work fine. There seems to be something special about this test case, maybe having to do with these particular dependent artifacts. It's possible there is some problem with transitive dependencies? But I'm just guessing. Also see http://jira.codehaus.org/browse/MJAVADOC-102, which I reported recently. Because of that bug, the error messages we're seeing here could be misleading side-effects that hide that root cause of the problem. > Simple test case where compile succeeds but javadoc fails > --------------------------------------------------------- > > Key: MJAVADOC-103 > URL: http://jira.codehaus.org/browse/MJAVADOC-103 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Adam Lally > Attachments: maven-javadoc-test.zip > > > The attached project has a parent POM with one module. The module has just > one simple Java class in it, but it has dependencies on some 3rd party > artifacts (available from a shared repository). > When I run "mvn install" for the parent, it succeeds. > If I run "mvn javadoc:javadoc" from the module, it succeeds. > If I run "mvn javadoc:javadoc" from the parent, it fails: > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] An error has occurred in JavaDocs report generation. > Embedded error: Exit code: 1 - > C:/alally/dev/maven-javadoc-test/test-module/src/ > main/java/Test.java:3: package org.eclipse.jdt.ui does not exist > import org.eclipse.jdt.ui.ISharedImages; > ^ > C:/alally/dev/maven-javadoc-test/test-module/src/main/java/Test.java:4: > package > org.eclipse.jdt.ui does not exist > import org.eclipse.jdt.ui.JavaUI; > ^ > C:/alally/dev/maven-javadoc-test/test-module/src/main/java/Test.java:5: > package > org.eclipse.swt.graphics does not exist > import org.eclipse.swt.graphics.Image; > ^ > C:/alally/dev/maven-javadoc-test/test-module/src/main/java/Test.java:8: > cannot find symbol > symbol : class Image > location: class test.module1.Test > public static final Image CLASS_ICON= > JavaUI.getSharedImages().getImage(IShare > dImages.IMG_OBJS_CLASS); > ^ > C:/alally/dev/maven-javadoc-test/test-module/src/main/java/Test.java:8: > cannot find symbol > symbol : variable ISharedImages > location: class test.module1.Test > public static final Image CLASS_ICON= > JavaUI.getSharedImages().getImage(ISharedImages.IMG_OBJS_CLASS); > ^ > C:/alally/dev/maven-javadoc-test/test-module/src/main/java/Test.java:8: > cannot find symbol > symbol : variable JavaUI > location: class test.module1.Test > public static final Image CLASS_ICON= > JavaUI.getSharedImages().getImage(ISharedImages.IMG_OBJS_CLASS); -- 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
