You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matt Kern (JIRA)" <ji...@codehaus.org> on 2007/05/02 13:43:26 UTC
[jira] Commented: (MJAVADOC-103) Simple test case where compile
succeeds but javadoc fails
[ http://jira.codehaus.org/browse/MJAVADOC-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94782 ]
Matt Kern commented on MJAVADOC-103:
------------------------------------
[ This post is just to help others who might stumble across this bug looking for a solution to a problem I had ]
I saw this exact issue using the maven-psteclipse-plugin v1.1.0 (direct from pst) and the maven-javadoc-plugin v2.2. The issue I had was that the psteclipse:update goal is bound to the process-resources lifecycle stage. Running "mvn javadoc:jar" would fail in the master directory but succeed in the child (project) directories. However, running "mvn psteclipse:update javadoc:jar" from the master directory got around this problem. I suspect there is still something wrong somewhere, but at least this allowed me to proceed.
> 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
> Assignee: Vincent Siveton
> Fix For: 2.1
>
> 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