-I have found that previous versions of Launch4j simply places java .class file contents,
pretty much as they are, into one file and surrounds them with other content. What this
has meant is that those .class files can just be directly copied and pasted out of the resulting
target Launch4j file. Has the .class file encoding in the target changed, eliminating
this issue, or not?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To be precise, launch4j can wrap a jar, but does not itself create such file out of loose class files. No changes were made in this regard. The jar files are only wrapped for convenience but not to protect your application in any way. You can use an obfuscator for thay purpose, for example ProGuard.
Grzegorz
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-I have found that previous versions of Launch4j simply places java .class file contents,
pretty much as they are, into one file and surrounds them with other content. What this
has meant is that those .class files can just be directly copied and pasted out of the resulting
target Launch4j file. Has the .class file encoding in the target changed, eliminating
this issue, or not?
To be precise, launch4j can wrap a jar, but does not itself create such file out of loose class files. No changes were made in this regard. The jar files are only wrapped for convenience but not to protect your application in any way. You can use an obfuscator for thay purpose, for example ProGuard.
Grzegorz