java.util.NoSuchElementException when using maven 2.0.6 and 2.0.7, but works in
2.0.4
-------------------------------------------------------------------------------------
Key: MJAVADOC-143
URL: http://jira.codehaus.org/browse/MJAVADOC-143
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: AIX
Reporter: apache maillist
under JDK 1.4
works in 2.0.4 with /usr/bin/maven-2.0.4/bin/mvn javadoc:javadoc
in 2.0.6
I run the following, and it works.
/usr/bin/maven-2.0.6/bin/mvn
org.apache.maven.plugins:maven-javadoc-plugin:2.2:javadoc
.....
.....
.....
[INFO] [javadoc:javadoc]
[WARNING] -notimestamp option is not supported on Java version < 1.5
[WARNING] -sourcetab option is not supported on Java version < 1.5
Loading source files for package org.kp.messagingservice.query...
Loading source files for package org.kp.messagingservice.spi...
Loading source files for package org.kp.messagingservice.vo...
Constructing Javadoc information...
Standard Doclet version 1.4.2
But if I run the following, it gives me the java.util.NoSuchElementException
error.
/usr/bin/maven-2.0.6/bin/mvn
org.apache.maven.plugins:maven-javadoc-plugin:2.3:javadoc
........
........
........
[INFO] [javadoc:javadoc]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(StringTokenizer.java(Compiled
Code))
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocVersion(AbstractJavadocMojo.java:2959)
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1085)
at
org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:131)
at
org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:219)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
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:224)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
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)
--
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
