Skip to content

Modify ModularJarArchiver to use the manifest main class as default #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

plamentotev
Copy link
Member

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.
@plamentotev plamentotev added this to the 3.7.0 milestone Sep 30, 2018
@plamentotev plamentotev deleted the manifest-overrides-main-class branch September 6, 2022 06:14
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.

1 participant