Uploaded image for project: 'BlueJ'
  1. BlueJ
  2. BLUEJ-379

Classes with dependency to uncompiled class sometimes not marked uncompiled

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Low
    • Resolution: Done
    • Affects Version/s: 2.5.3
    • Fix Version/s: 3.0.6
    • Component/s: PkgMgr

      Description

      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:

      public static B bObject = new B();
      

      ... 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.

        Attachments

          Activity

            People

            • Assignee:
              davmac Davin McCall
              Reporter:
              davmac Davin McCall
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: