StringIndexOutOfBoundsException on parsing the files

The 'org.apache.commons.collections.set.ListOrderedSet: method <init>()V not found' part of the log is probably the relevant issue. Which version of the javadoc plugin are you using? We had a binary-incompatible dependency on commons-collection-3.1 in some intermediary versions of the plugin, can you try the latest snapshot? If that doesn't help, a small test case would be useful since I can't reproduce this.

Thanks for looking at it Lukas.

The error occurred with the standard version(s) shipped with b1 and b2. I know b2 shipped with 1.7, which I still am running.

I just tried the 1.8-SNAPSHOT from cvs.apache.org. (date of 12/9/05), and it still has the problem:

Caught exception evaluating: org.apache.commons.jexl.ExpressionImpl@7ec028. Reason: java.lang.StringIndexOutOfBoundsException: String index out of range: -64
java.lang.StringIndexOutOfBoundsException: String index out of range: -64

I am not sure how to create a small test case. I'm not sure if it is based on number of errors, number of files, or what. An in-progress small project (just getting going) has 104 .java files, and has the problem. Another smaller project with some common files has only 44 .java files but does not have the problem Two other main projects have thousands of .java files (about 2500 in one and almost 5000 in another) and they both have the problem.

Would having the javadoc-warnings.xml file for a problem one help? Is it crashing on parsing that file?

The report.txt file that is generated first by javadoc could maybe help. It crashes when transforming this file into javadoc-warnings.xml.
Also, can you set maven.javadoc.debug=true and check the stacktrace that follows right after the line '*** WARNING: exception parsing line ...'. If I understand correctly, this will be different from what you got above.

I can reproduce this problem with both Maven 1.1 beta1 and beta2 with a very simple project.xml (from the 10 minute test doc) and a simple java file which has a single javadoc error (missing @param).

I have attached this test project with this bug.

Thanks a lot Girish! This is almost too simple a test case to be interesting .
Now I can reproduce the problem running m11b2, but I don't see it anymore using the current development version m11b3-SNAPSHOT. That seems to confirm my initial suspicion that it is some kind of binary incompatibility between the maven core and the plugin. We have cleaned up a lot of dependencies since m11b2, which might have fixed this bug. Is there a chance that any of you could test and confirm that this is not an issue anymore in the latest maven from SVN?

b3 does not fix it for me .

I think the line in report.txt the parser crashes on is one that has the FQCN wrap to the next line. If you have a really long line in report.txt that wraps (basically from a long path & package name), does it crash for you?

E.g. here is mine:
[javadoc] C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\state\vantage\hm\batch\ar\policy\premiumcreator\package.html: warning - Tag @link: reference not found: us.state.vantage.hm.batch.ar.policy.premiumcreator.
[javadoc] PremiumCreatorStrategyCredit

This is a different issue - did you try with Girish's test project?

Inserting your line above into my report.txt file, I also get an exception with 11b3. That's because the warning comes from a package.html file, not a java source file. The parser expects the warning to be in the following format:

PATH_TO_JAVA_FILE:LINE_NUMBER: warning - WARNING_MESSAGE

Your line above doesn't contain a line number which leads to a NumberFormatException (I suppose this is the same you get).
Now I don't know why package.html shows up in your report, I thought that only java source files were scanned when generating the javadocs.
Any ideas?

The error in that package.html file is this line:

It errantly has the class name on the next line, causing a space before the class name.

From a quick review, I see we have other package.html files with other errors.

package.html is a special file for Javadoc. Placed in a Java source package, it becomes the "main page" displayed for a selected package in the generated Javadoc. It's a straight HTML file, plus any Javadoc tags, such as @link.

So it sounds like this error is an unsupported use case?

Here are a couple more of those messages as samples:

[javadoc] C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\state\vantage\hm\batch\ar\policy\premiumduedate\package.html: warning - Tag @link: reference not found: us.state.vantage.hm.batch.ar.policy.PremiumDueDateCalculatorReplacement

[javadoc] C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\state\vantage\hm\batch\ar\sql\package.html: warning - Tag @inheritDoc cannot be used in package documentation. It can only be used in the following types of documentation: method, inline text.

(this one is deliberately there as part of sample code - so need to find a way to "escape it".)

No NFE in sight. Actually, I get:
Caught exception evaluating: org.apache.commons.jexl.ExpressionImpl@cc5436. Reason: java.lang.StringIndexOutOfBoundsException: String index out of range: -64

There is a try-catch block in the parser class that swallows the first exception if not in debug mode. The SIOE is just a consequence of that but it has nothing to do with the original problem. You have to set maven.javadoc.debug=true to see the root cause of the problem.

Got it, thanks. Yes, with debug on, I see the NFE. Well, at least we now know what the problem is! Thank you for all the advice and knowledge to track it down.

Jeff, I just committed a fix to the javadoc-plugin svn, can you test please?

Checked out revision 355960. Built it and it ran great!!

These messages you added nicely show where the previous problems were

• • • WARNING: no line number found in 'C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\state\vantage\hm\batch\ar\policy\premiumduedate\package.html', setting to 0.

So the Javadoc HTML files (package.html, overview.html) with problems now correctly list in the Javadoc Warnings Report. Awesome!

Thank you very much for adding this use case to the Javadoc plugin.

Lukas, Do you plan to post another 1.8-SNAPSHOT at http://cvs.apache.org/repository/maven/plugins/ with this enhancement?

Done.