Skip to content

Check call flows passing JavaProject.NO_RELEASE into multi-release aware methods #5149

Description

@stephan-herrmann

During review of #4534 I identified the following call chains as passing JavaProject.NO_RELEASE where potentially a specific release should be passed (focus is in NameLookup):

Image

There might be more.

For each of the leaves where NO_RELEASE is passed, we need a justification or we need to improve.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions