Uploaded image for project: 'Java Parent Project'
  1. Java Parent Project
  2. JPAR-104 Support Java 11
  3. JPAR-113

Establish Automatic-Module-Name for "library" modules

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Java 9+ includes named modules. As people modularise their own applications, they want to start including their dependencies in their own module-info files.

      There's a transition mechanism for this in which non-modular .jar artifacts can be promoted to "automatic" modules with names initially based on their file names... which is not necessarily what we will want in all cases. However, once a dependent references a module in this way it's disruptive for them to change.

      There's a second mechanism which allows a pre-modular artifact to declare the module name it will use in the future by adding an Automatic-Module-Name declaration in its manifest.

      Ideally, we should head this issue off at the pass by figuring out what our future module naming scheme will be, and including Automatic-Module-Name declarations in our artifacts' next releases.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ian@iay.org.uk Ian Young
              Reporter:
              ian@iay.org.uk Ian Young
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 5 hours, 4 minutes
                  1d 5h 4m