Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Invalid character in input error when using javadoc

 
sri chitra
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am trying to execute javadoc command to get the 3-frame API for the following the packages xxx and xxx.yyy
The directory structure is
api
src
----overview.html
---- xxx
-------package.html
-------XXXClass1.java
-------yyy
---------package.html
---------YYYClass1.java
classes
-----xxx
-------XXXClass1.class
-------yyy
---------YYYClass1.class

The src files have just the package and class declarations
package xxx;
import yyy.*;
public class XXXClass1 {
}

package xxx.yyy;
public class YYYClass1 {
}
The javadoc command is executed from the src directory.
javadoc -d ../api -overview overview.html -classpath ../classes -sourcepath . xxx xxx.yyy
But I am getting the following error
Loading source file xxx...
Loading source files for package xxx.yyy...
xxx: Invalid character in input.
xxx: Class or interface declaration expected.
xxx: Invalid character in input.
xxx: Invalid character in input.
xxx: Invalid character in input.
.
.
.
Can anybody help me in fixing this?
Thanks,
chitra
 
Michael Ernest
High Plains Drifter
Sheriff
Posts: 7292
Netbeans IDE VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The first and best check is to make sure these classes compile. If they do, then chances are you're running into a javadoc bug. There's only one way to trace that, I'm afraid, and that's by processing one file at a time.
 
sri chitra
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The classes compile fine.
Generating 2-frames API works fine. But
3-frames API does give the error.
I am using javadoc 1.2 version in the solaris
environment.
Is there anyway I can find the javadoc command
that was used to generate the Java API?
Thanks,
chitra
 
sri chitra
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I removed the -classpath option completely and it
worked fine.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic