[ http://jira.codehaus.org/browse/MJAVADOC-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Luck closed MJAVADOC-113. ------------------------------ Resolution: Fixed Fix Version/s: 2.3 Thanks guys. This is working now for my use case using 2.3-SNAPSHOT from the Apache People repo. I have changed over to it. > docletPath not working in 2.2 - Cannot find doclet class > ydoc.doclets.YStandard > ------------------------------------------------------------------------------- > > Key: MJAVADOC-113 > URL: http://jira.codehaus.org/browse/MJAVADOC-113 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Greg Luck > Fix For: 2.3 > > > I have two projects which use the javadoc plugin. Ehcache and JPam. > Both started giving this error in the last few days: > [INFO] Velocity successfully started. > [INFO] [javadoc:javadoc] > [WARNING] No docletpath option was found. Please review <docletpath/> or > <docletArtifact/> or <doclets/>. > 1 error > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - > javadoc: error - Cannot find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred > in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot find > doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: An error has > occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot > find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > at > org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:230) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - > javadoc: error - Cannot find doclet class ydoc.doclets.YStandard > Command line > was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc > -J-Xmx512m -J-Xms128m @options @packages > at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1200) > at > org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:128) > at > org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:216) > ... 18 more > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 18 seconds > [INFO] Finished at: Sun Feb 25 09:48:18 EST 2007 > [INFO] Final Memory: 9M/17M > [INFO] > ------------------------------------------------------------------------ > Reverting to 2.0 by adding a version identifier of 2 fixes the problem: > <!-- javadoc --> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-javadoc-plugin</artifactId> > <version>2.0</version> > </plugin> > If 2.0 works and 2.2 does not, is this a bug in 2.2 javadoc, or is it a bug > in the parent project: org.apache.maven.plugins. The version in 2.2 is 4, in > 2.0 it was 3. > <parent> > <artifactId>maven-plugins</artifactId> > <groupId>org.apache.maven.plugins</groupId> > <version>4</version> > </parent> > I am working around by staying on 2.0. -- 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