File details missing when creating an EXE file on Mac OS X with l4j 3.9
Brought to you by:
grzegok
If I check file properties of a launch4j executable (right click => properties => details) created on Mac OS X, you can see that many details are missing.
Attached is a screenshot of one of my programs. The file name in the title bar shows which one was created in Mac OS X (Sierra) and which one on Windows 10.
Both were manually created using the latest standalone version 3.9
Other people have ran into this issue as well...
follow up the latest comments starting from here: https://github.com/lukaszlenart/launch4j-maven-plugin/issues/50#issuecomment-280459051
Yes, I know about it, I tried to help Łukasz but it seems the problem is associated with windres.
Which package are you using launch4j-3.9-macosx-x86-10.8.tgz or launch4j-3.9-macosx-x86.tgz ?
I'm using the package launch4j-3.9-macosx-x86.tgz on macOS 10.12.3 "Sierra"
Please use the package launch4j-3.9-macosx-x86-10.8.tgz as it solves the exact same problem for me on macOS Sierra.
Thanks for the information, Thomas! Unfortunately the launch4j-maven-plugin still uses the "default" package...
In version 3.9 there are two: launch4j-3.9-workdir-mac.jar and launch4j-3.9-workdir-osx.jar. osx is the 10.8 version. Make sure you are using the latest plugin version, you can also ask for support there: https://github.com/lukaszlenart/launch4j-maven-plugin
Good news: The new version 1.7.16 of the launch4j-maven-plugin detects different OSX versions to properly use the proper binary bundle.
I'm sorry, I'm confused now. I would have expected that the download package "launch4j-3.9-macosx-x86-10.8.tgz" is for Mac OS X 10.8 and below and "launch4j-3.9-macosx-x86.tgz" is for newer versions, like Sierra. Not speaking about the maven workdir jars, but the downloads from sourceforge...
@Grzegorz can you enlighten us?
It is the other way around, the package launch4j-3.9-macosx-x86.tgz was available first, and the 10.8 was added later. Since the support for 10.8 has ended it makes no sense to keep the even older package. So I will drop it and leave only one, this will also solve the plugin problem.
Removed old package, leaving only one.