Summary: | Operation not supported in JLS2 AST from resolving MethodBinding | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Rob Grzywinski <rgrzywinski> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.1 | ||
Target Milestone: | 3.1 RC1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Rob Grzywinski
2005-05-17 08:59:07 EDT
I will investigate it. JLS3 doesn't mean it is for 1.5 code only. JLS3 can be used for any kind of code. This is a bug, but you should definitely move your code to JLS3. I know that I have to move to JLS3 eventually but I was hoping to put it off as long as possible. I was using JLS2 to allow me to cull out a number of things that I didn't want to have to think about yet. I guess that now is as good a time as any to get off my lazy keister. Is JLS2 a priority for 3.1? I'm assuming "yes" for backwards compatibility. I would say yes. JLS2 should work. Added a protection for JLS3. isVarargs() is only used if the api level is greater or equals to JLS3. Fixed and released in HEAD. Regression test added in org.eclipse.jdt.core.tests.dom.ASTConverterTest2.test0606 Verified for 3.1 RC1 with build I20050527-0010. Confirm verified in 3.1 RC1 Thanks! |