Skip to content

Add Automatic-Module-Name to MANIFEST.MF#279

Merged
Michael Barker (mikeb01) merged 1 commit intoLMAX-Exchange:masterfrom
matteodri:automatic-module-name
Feb 10, 2020
Merged

Add Automatic-Module-Name to MANIFEST.MF#279
Michael Barker (mikeb01) merged 1 commit intoLMAX-Exchange:masterfrom
matteodri:automatic-module-name

Conversation

@matteodri
Copy link
Copy Markdown
Contributor

This is the first step in the process of modularizing the Disruptor JAR #234.
Adding Automatic-Module-Name in the manifest file makes the library usable as a Java automatic module without moving the library itself to Java 9 (or later) or creating a module-info.java.
This allows the Disruptor when loaded as an automatic module to get its name from the Automatic-Module-Name entry in MANIFEST.MF instead of being inferred from the filename. This second option is dangerous as filenames are far from being unique and stable.
This post explains the point of having an Automatic-Module-Name defined: http://branchandbound.net/blog/java/2017/12/automatic-module-name/

Adding Automatic-Module-Name in the manifest file makes the library usable as a Java automatic module preventing possible clashes of the name with other libraries.
@mikeb01 Michael Barker (mikeb01) merged commit 9ee250d into LMAX-Exchange:master Feb 10, 2020
@matteodri Matteo Dri (matteodri) deleted the automatic-module-name branch February 16, 2020 20:41
@rgoers
Copy link
Copy Markdown

Log4j 2 uses the disruptor. One of the goals of Log4j 2 3.x is to fully modularize all of our deliverables, so we need a released version that includes the automatic module name. When can we expect this in a release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants