BUG: JDeveloper code editor shows valid static import call as error

Question

I've noticed what appears to be a bug in the JDeveloper code validator when dealing with static imports.
The following classes demonstrate the problem:
package test;
public class Parent {
  public static void parentMethod() {
    System.out.println("called parentMethod.");
package test;
public class Child extends Parent {
  public static void childMethod() {
    System.out.println("called childMethod.");
package test;
import static test.Child.*;
public class StaticInheritanceTest {
  public static void main(String[] args) {
    Child.childMethod();
    Child.parentMethod();
    childMethod();
    parentMethod();  //<-- this line is highlighted as an error
}Notice how on lines 7 and 8 of StaticInheritanceTest, the code validator does recognise that both parentMethod and childMethod are static methods of the Child class.
Since 'Child' has been statically imported, then parentMethod should be available. Although parentMethod is presented as an 'auto-suggest' at line 11 in StaticInheritanceTest, when you try to call it the code editor shows the call as an error and the Ctrl-Click (to drill down into the method) doesn't work.
When I run the class, it compiles successfully and runs with the following output:
called childMethod.
called parentMethod.
called childMethod.
called parentMethod.This might seem like an obscure and theoretical problem, but I've hit this whilst using Mockito, which uses exactly this kind of inherited static method to provide matchers.

Answer 1

Hi,
thanks. Will file a bug. This seems to be a designtime only issue that does not present a show stopper.
Frank