Should NameEnvironment.computeClasspathLocations() consider the release also for source locations?

[stephan-herrmann]

Method NameEnvironment.computeClasspathLocations(IWorkspaceRoot, JavaProject, Map<IProject, ClasspathLocation[]>, int) may use the releaseTarget to

• distinguish modular / non-modular builds
• filter output folders
• select the correct module-info.java (with Implement per-source-folder module-info for multi-release compilation #4534)

I would think that also sourceLocations should be filtered in MR projects. This should then be done before any ModulePathEntry is created (which holds a reference to all applicable source locations).