Skip to content

[BLUEJ-379] Classes with dependency to uncompiled class sometimes not marked uncompiled

It's possible to have a class A with a dependency on another class B, where B is not compiled, but A will be shown as compiled when the package is loaded. For instance if A has a field:

{noformat} public static B bObject = new B(); {noformat}

... and the file B.class is deleted before starting BlueJ, this problem will manifest \- B will be shown as uncompiled, but A will show as compiled and can be inspected or (unsuccessfully) instantiated.

Issue metadata

  • Issue type: Bug
  • Priority: Low
  • Fix versions: 3.0.6