Skip to content

Inconsistent use of versionsuffix for Java #16038

@Micket

Description

@Micket

First, we have been sloppy with versionsuffixes for Java.

E.g.

  • ant-1.10.12-Java-17.eb
  • Nextflow-22.04.0.eb (depends on Java-11)
  • ANTLR-2.7.7-GCCcore-11.3.0-Java-11.eb (uses the "2022a" toolchain hierarchy default)
  • Bazel-5.1.1-GCCcore-11.3.0.eb (depends on Java-11)

so maximum inconsistency here.

I'd say that at least every SYSTEM level Java app should include a suffix since they are independant of toolchain versions, there is no "default". That means Nextflow should have added a suffix here.
For things under toolchains, for anything that needs the non-default Java, adding the suffix should of course be done.

That leaves stuff like ANTLR and Bazel. There is no harm in adding the suffix for added visibility so I don't mind if we just add it to everything.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions