Skip to content

Allow disabling Multi-Release #1661

@Gaming32

Description

@Gaming32

What feature do you want to see added?

Currently, if any dependency is Multi-Release, the MANIFEST.MF is forced to have Multi-Release: true. Currently this causes issues in my use-case, as Multi-Release is getting set to true with no versions folder being generated because my dependency has only a module-info.class in this directory.

Upstream changes

No response

Are you interested in contributing this feature?

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions