Skip to content

Sort out classpath-related licenses issues #750

@pombredanne

Description

@pombredanne

We have a bit of a mess to sort out for the classpath exception-related licenses.

Historically we have these:

  • gpl-2.0-library: this is a notice with a GPL (version unspecificed)
    and most of the classpath-exception text except for the first paragraph.
    This should not be a license but a rule instead

  • gpl-2.0-independent-module-linking: this is a notice of gpl-2.0-plus with
    classpath-exception-2.0. This should not be a license but a rule instead
    This was used in https://github.com/icsharpcode/SharpZipLib which has since switched to MIT

  • gpl-2.0-oracle-openjdk: this is a notice of gpl-2.0-plus with
    classpath-exception-2.0. This should not be a license but a rule instead

  • gpl-2.0-openjdk: this is a notice of gpl-2.0-plus with
    classpath-exception-2.0 and the assembly exception
    The combo of classpath with assembly exception is rather unique. I think we
    should create a new exception for the combo "classpath-exception-2.0 +
    the assembly exception and call this the openjdk-exception

  • gpl-2.0-classpath: this is IMHO to be replaced by classpath-exception-2.0.
    In particular the calsspath exception is not specific to a version of the GPL

Recently, SPDX added this:

  • classpath-exception-2.0

So after rework we would end up with:

  1. several new rules and tests
  2. classpath-exception-2.0 as a license exception
  3. openjdk-exception as a new license exception that contains the classpath exception and the assembly exception texts http://openjdk.java.net/legal/assembly-exception.html

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