Skip to content
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

Ensure main classes from inputs take precedence before those found in JARs added to the class path #3165

Merged

Conversation

Gedochao
Copy link
Contributor

Fixes #3137

@Gedochao Gedochao force-pushed the maintenance/fix-main-classes-priorities branch from c2b75ac to b6928e5 Compare September 11, 2024 07:29
@Gedochao Gedochao marked this pull request as ready for review September 11, 2024 13:54
Copy link
Member

@tgodzik tgodzik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Gedochao Gedochao merged commit 142163b into VirtusLab:main Sep 12, 2024
78 checks passed
@Gedochao Gedochao deleted the maintenance/fix-main-classes-priorities branch September 12, 2024 13:41
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.

problems if one or more jars in classpath have "Main-Class" defined in MANIFEST.MF
2 participants