Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Sep 30, 2018

If the main class for a module is not explicitly set, lets use the one specified in the manifest file. That would simplify the creation of modular JAR files - clients should just set the manifest main class as in non-modular JAR file and everything will work out of the box. Also it will allow ModularJarArchiver to be used as drop-in replacement of JarArchiver without any additional configuration.

If the main class for a module is not explicitly set, lets use
the one specified in the manifest file. That would simplify the
creation of modular JAR files - clients should just set
the manifest main class as in non-modular JAR file and
everything will work out of the box. Also it will allow
`ModularJarArchiver` to be used as drop-in replacement of
`JarArchiver` without any additional configuration.
@ghost ghost added the enhancement label Sep 30, 2018
@ghost ghost added this to the 3.7.0 milestone Sep 30, 2018
@ghost ghost closed this in 89e8b75 Oct 10, 2018
@ghost ghost deleted the manifest-overrides-main-class branch September 6, 2022 06:14
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants