-
Notifications
You must be signed in to change notification settings - Fork 133
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
Ubuntu run failure without wrapjar set to false #382
Comments
Hi @akhilmanikandan! I've been doing some tests with DEB package generation, trying with So, do you mean that it fails when setting |
The only thing I've not tried yet is using a customized fat jar. Maybe this could be the problem. |
I've just tested it using a fat jar without problems. If you are bundling all your dependencies in a fat jar, you should set |
the problem seems to be size, if the fat jar is small it works, looks like exisiting issues with big jars in launch4j |
But your problem wasn't in Ubuntu? Anyway, JP supports other kind of EXE files for Windows |
issue is across ubuntu and windows , its the same issue, something to do with packaging, it works if i create a small fat jar and class not found when i create a fat jar above 120mb |
I'm submitting a…
Short description of the issue/suggestion:
DEB package for ubuntu not working when true
Steps to reproduce the issue/enhancement:
3.running the executable yields following error
Error: An unexpected error occurred while trying to open file ##########
What is the expected behavior?
The deb file works with wrapjar set to true
What is the current behavior?
The package is not working with wrapped jar in executable
Do you have outputs, screenshots, demos or samples which demonstrate the problem or enhancement?
What is the motivation / use case for changing the behavior?
want to package the jar inside the executable to hide the jar file from the user
Please tell us about your environment:
Other information (e.g. related issues, suggestions how to fix, links for us to have context)
The text was updated successfully, but these errors were encountered: