-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Maven generated dmg file is not working #39
Comments
The problem is not really related to the DMG file. I just realized that non of the generated
|
Also I had to upgrade the version of launch4j in the
|
None, I copied the code for launch4j and it seemed to worked so I left it be :D |
Do you have oracle java or openjdk? And is it java 8? |
I found out that I was able to "fix" this by removing the following code section from the
Can you explain if this is really required and how can this result in an error on MacOS (I am using Maven version 3.6.3) Hmmmm. Of course this does not really solve the situation as the Client as able to launch but fails to load the resources.... |
|
The Launch4j error should not be related to the JAR problem. I think this was only because the version of the plugin was so old that it shipped 32bit binaries instead of 64 bit ones. |
Additionally I was wondering if the
|
The section is there because resources are kept in non standard location, interesting that it launches without them tho. I will check if I have openjdk or oracle java on my PC, it might be openjdk specific problem. |
The manifests are there because they didn't cause any problem for me, so I simply ignored them. Removing them.might solve the issue since maven should generate proper manifest regardless. |
Try looking at maven shade plugin as it is responsible for packaging all the things into jar. With current configuration it throws warnings about overlapping Manifest but the warning says it shouldn't cause any problems. |
UPDATE: After removing the manifests the jar file launches and also the
I will have a look at your changes from #36 |
Just to document the warning here:
|
Try looking at the ImageManager method defineImage, that should be the root cause. I will investigate that once I get back.to the computer. |
I wasn't able to reproduce it with OpenJDK on Ubuntu. I also looked at the generate Manifest files and they seem alright and the missing class is present in the jar, so it is probably mac only issue, but I have no idea why.
|
Small progress: Fixed the image loading on macOS by replacing
with
Case sensitivity lol... Still have to figure something else but I will let you know when I made progress. |
Still no success but it seems to be about case sensitivity as well. The contents of the @pehala Could you possibly provide me the output of |
http://one-line-it.blogspot.com/2013/01/mac-os-x-java-becomes-case-insensitive.html
|
Here is an example of the situation. Contents of the JAR file:
How it should look like:
|
Here it is https://pastebin.com/3LuNC8Ns, but it looks like it is identical to yours. |
If the problem is with case sensitivity, we can simply rename resources to lowercase, or separate resources into custom folder. |
My workaround was renaming Like you already motioned, separating the resources to a custom folder would be a good idea. Do you have a recommendation for the directory name and how to realize this in maven? |
I can create reorganization PR which would address it. I wanted to do rename directories to proper maven ones like src/main/java and src/main/resources anyway. |
That would be so great! I hope the effort to do so is not to much... |
As discussed in #36, it seems as the .dmg is not working correctly.
The text was updated successfully, but these errors were encountered: