Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8188035

JavaFileManager.listLocationsForModules does not always reflect values set through StandardJavaFileManager.setLocationForModule.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 9, 10
    • Fix Version/s: 10
    • Component/s: tools
    • Subcomponent:
    • Resolved In Build:
      b28

      Description

      When setLocationForModule is used, and then JavaFileManager.listLocationsForModules is used, then for (some locations), the listed locations won't include the changes through setLocationForModule. In particular the locations handled by Locations.ModulePathLocationHandler are affected, because it will list modules based on the searchPath and ignore the ModuleTable.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jlahoda Jan Lahoda
                Reporter:
                jlahoda Jan Lahoda
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: