Skip to content

Mill should add the multi-release jar file attribute to the created uber jar file if one of the input jar files is a multi-release jar. #2729

Open
@Flowdalic

Description

@Flowdalic

Mill should add the multi-release jar file attribute to the created uber jar file if one of the input jar files is a multi-release jar.

Right now, mill users have to manually add

  def manifest = super.manifest().add(
    "Multi-Release" -> "true"
  )

to their build.sc if one of the input jar files is a multi-release jar file and if they want the JVM to use the most suitable classes depending on the JVM version. Otherwise, this may leads to superfluous warnings because of code paths for older JREs being used.

This is (probably) the right fix, instead of #2724

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