-
Notifications
You must be signed in to change notification settings - Fork 36
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
Crash when trying to run a product built with buildProduct #302
Comments
Hello @icedevml! I have a reproducer on macOS for this one. I can only assume this is a dependency conflict - either Gretty ships multiple competing versions of apache-commons-cli, or we have an incompatibility between groovy-cli-commons and apache-commons-cli. The order on the classpath can vary from one JRE to the next, or from one operating system to the other. As a workaround, can you try and delete |
Hello @f4lco and thanks for your help. I can confirm that the issue is resolved with the workaround that you have provided. Gretty runs succesfully through And yeah, I was even comparing hashes of all the build artifacts. They are exactly the same, so I think that you are right. It must be the difference in the classpath precedence across Windows and UNIX systems. |
@f4lco By the way, not sure if it's related, but:
So there at least two versions of the |
Hello,
I'm using Ubuntu Jammy (22.04.3 LTS) with OpenJDK 17 and gradle version 7.3. I'm running gretty in 4.1.1 version.
Whenever I build the product using
gradlew buildProduct
, I'm getting the following exception when trying to run it using the generatedrun.sh
script:I've tried to upgrade to gradle 8.5 with OpenJDK 21 - the issue is exactly the same. I've also changed the Ubuntu version to the latest one and it doesn't help too.
The same codebase builds and runs fully correctly on Windows, under exactly the same OpenJDK versions.
I would like to kindly ask you for assistance with debugging this one. I feel like I've already looked at it from every possible angle and I can't spot what is wrong. The crash is somewhat very early and related with some CLI arguments parsing in runner, although I don't fully understand what really happens there.
Could you please provide some guidance on how to troubleshoot the issue?
The text was updated successfully, but these errors were encountered: