Summary: | StringIndexOutOfBoundsException in at org.eclipse.jdt.internal.core.JavaModelManager | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Nicolás Lichtmaier <nico.lichtmaier> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | VERIFIED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | clg-business, philippe_mulet |
Version: | 3.2.2 | ||
Target Milestone: | 3.4 M2 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Nicolás Lichtmaier
2007-03-17 04:05:37 EDT
Sounds similar to bug 164707... Please attach the org.eclipse.jdt.core.prefs of this project (you'll find it in .settings directory) to confirm this assumption. Thanks Philippe, sounds clear that we surely need to backport the fix for this bug... My org.eclipse.jdt.core.prefs file was: org.eclipse.jdt.core.compiler.codegen.targetPlatform=6 eclipse.preferences.version=1 org.eclipse.jdt.core.compiler.source=6 org.eclipse.jdt.core.compiler.compliance=6 I've removed the project specific compiler settings and now everything works, thanks =). Uhm, If I correctly read the patch at bug 164707, versionToJdkLevel() will fail to recognize "6.0" as a JDK1_6... Why not just do: if(versionID.startsWith("1.")) versionID = versionID.substring(2); ... and check agains "1", "2", "3"... (In reply to comment #4) > Uhm, If I correctly read the patch at bug 164707, versionToJdkLevel() will fail > to recognize "6.0" as a JDK1_6... > > Why not just do: > > if(versionID.startsWith("1.")) > versionID = versionID.substring(2); > > ... and check agains "1", "2", "3"... > The bug is in Maven as they directly modify the org.eclipse.jdt.core.prefs file instead of using API methods of IJavaProject... As these values are internal, for obvious performance reason, we're *only* expecting them and do not want to accept/verify all possible ones... Sorry for the late answer but close this bug as WONTFIX Use API to modify org.eclipse.jdt.core.prefs file Verified for 3.4 M2 using build I20070917-0010. |