We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using enableManifestClasspath, the main module jar is not added to the generated classpath.
As a result, the main class cannot be resolved and the application fails to start.
The problem can also be observed by comparing the classpath generated with and without the enableManifestClasspath flag.
The text was updated successfully, but these errors were encountered:
Add project output jar to the generated MANIFEST
4b135ad
This is to resolve palantir#476
Assert presence of project jar in jar MANIFEST
43b7c53
Test for resolution of palantir#476
24d9477
Fix missing jars in classpath of generared in jar MANIFEST (#477)
e5068c6
fixes #476 Classpath in jar MANIFEST now contains the project jars and is consistent with the classpath generated in launcher script.
Successfully merging a pull request may close this issue.
When using enableManifestClasspath, the main module jar is not added to the generated classpath.
As a result, the main class cannot be resolved and the application fails to start.
The problem can also be observed by comparing the classpath generated with and without the enableManifestClasspath flag.
The text was updated successfully, but these errors were encountered: