Bug 120847

Description Frederic Fusier 2005-12-14 06:54:04 EST

Verifying bug 120559 with build I20051214-0010, I got an AIOOBE with following test case:

1) Create a project
2) Add external library to this project (whatever you want it does not matter)
3) Edit Javadoc location and enter a valid location (file:/D:/tmp/doc/ for example)
4) Click OK on all dialogs to validate your changes
5) Edit .classpath file and modify Javadoc location by hand to make it invalid
   (D:/tmp/doc/ for example)
6) Open Javadoc view
7) Select a class in the external library => AIOOBE:
java.lang.ArrayIndexOutOfBoundsException: 0
	at org.eclipse.jdt.internal.core.JavaModelStatus.getMessage(JavaModelStatus.java:364)
	at org.eclipse.core.runtime.CoreException.<init>(CoreException.java:42)
	at org.eclipse.jdt.core.JavaModelException.<init>(JavaModelException.java:70)
	at org.eclipse.jdt.internal.core.JavaElement.getLibraryJavadocLocation(JavaElement.java:678)
	at org.eclipse.jdt.internal.core.JavaElement.getJavadocBaseLocation(JavaElement.java:642)
	at org.eclipse.jdt.internal.core.BinaryType.getJavadocContents(BinaryType.java:1034)
	at org.eclipse.jdt.internal.core.BinaryType.getAttachedJavadoc(BinaryType.java:990)
	at org.eclipse.jdt.ui.JavadocContentAccess.getHTMLContentReader(JavadocContentAccess.java:121)
	at org.eclipse.jdt.internal.ui.infoviews.JavadocView.getJavadocHtml(JavadocView.java:467)
	at org.eclipse.jdt.internal.ui.infoviews.JavadocView.computeInput(JavadocView.java:399)
	at org.eclipse.jdt.internal.ui.infoviews.AbstractInfoView$2.run(AbstractInfoView.java:456)

I agree that it's not a common scenario as user is not intended to modify .classpath by hand, however it may happen and we must be safe about that.

It seems that at JavaElement.getLibraryJavadocLocation(JavaElement.java:678), built status does not have any JavaElement and message is expecting one for this ID...