feat: add an Automatic-Module-Name entry to the jar manifest

io7m · web-flow · commit ee0672454fd2 · 2020-05-01T11:21:33.000+02:00
This adds an Automatic-Module-Name manifest entry in order to allow epubcheck to be used in a modular context without having to depend on an unstable generated module name. The module name is `org.w3c.epubcheck`, which is already used as the bundle symbolic name in OSGi. Fixes #1128
diff --git a/pom.xml b/pom.xml
@@ -301,6 +301,7 @@
                             net.sf.saxon.*;version="[9.8.0,9.8.1)",
                             *
                         </Import-Package>
+                        <Automatic-Module-Name>org.w3c.epubcheck</Automatic-Module-Name>
                         <_removeheaders>Include-Resource,Private-Package, Bnd-LastModified, Build-Jdk, Built-By</_removeheaders>
                     </instructions>
                 </configuration>

Original file line number	Diff line number	Diff line change
`@@ -301,6 +301,7 @@`
`301`	`301`	`net.sf.saxon.*;version="[9.8.0,9.8.1)",`
`302`	`302`	`*`
`303`	`303`	`</Import-Package>`
	`304`	`+ <Automatic-Module-Name>org.w3c.epubcheck</Automatic-Module-Name>`
`304`	`305`	`<_removeheaders>Include-Resource,Private-Package, Bnd-LastModified, Build-Jdk, Built-By</_removeheaders>`
`305`	`306`	`</instructions>`
`306`	`307`	`</configuration>`