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
Breaking change when bundling JRE on Mac in 1.2.0+ #125
Comments
Hi @ogerardin! |
Sure, here's the output of
|
Fixed in issue-125 branch and changes merged into master. I'm going to release v1.6.0, with this and other changes. Thanks! |
JavaPackager v1.6.0 released to Maven Central |
Thanks! Unfortunately it's not available on Maven central yet https://search.maven.org/artifact/io.github.fvarrui/javapackager |
Finally got a chance to test again and it's now working as expected. Thanks! |
Great! |
I'm submitting a…
Short description of the issue/suggestion:
I'm building on Mac, in my configuration I have:
which is a valid JRE.
In 1.1.0 it works as expected.
In 1.2.0 and later versions, I get an error:
Starting with 1.5.1 there is a warning before it fails:
This leads me to believe that "/Contents/Home" is appended to the value of jrePath if it doesn't end with /Contents/Home. This might be correct for a JDK but not for a JRE when it is embedded in the JDK. In any case it should be checked if the specified path is a valid JRE (which it is) before trying to fix it.
Steps to reproduce the issue/enhancement:
Use version of plugin 1.2.0 or later
Specify in configuration:
Run
mvn package
on a MacWhat is the expected behavior?
JRE is bundled successfully as with JavaPackger 1.1.0
What is the current behavior?
Maven build fails with error:
Do you have outputs, screenshots, demos or samples which demonstrate the problem or enhancement?
What is the motivation / use case for changing the behavior?
This is a breaking change, it should work as in 1.1.0
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: