Recent changes to 137: [4.0.0] Consider renaming executable and library

#137 [4.0.0] Consider renaming executable and library

Michael Osipov — Thu, 26 Mar 2020 09:04:42 -0000

This sounds like an option at first glance, but at the end it isn't one. I don't have a specific application I use with JSW. I do maintain the FreeBSD Port of and expect for the ports using it the rest remains anonymous to me. I don't want to start to explain why I have renamed the artifacts, that they have to change config files and properties. I just expect a sane default name.

I would go with your option if I would have a private, isolated application.

#137 [4.0.0] Consider renaming executable and library

Michael Osipov — Thu, 19 Mar 2020 11:43:56 -0000

Leave me a couple of days to digest this...

#137 [4.0.0] Consider renaming executable and library

Leif Mortenson — Thu, 19 Mar 2020 10:15:47 -0000

Thanks for the feedback. This is already something we have discussed internally a couple times. But it would cause more confusion for long time users.
As is the Wrapper already allows you to change the wrapper binary name to anything you wish. Likewise the jar file can also be modified. I usually name it wrapper-3.5.43.jar in our applications.

The wrapper.native_library property also allows you to modify change the base bane of the native library.
https://wrapper.tanukisoftware.com/doc/english/prop-native-library.html

Please let me know how these work for you.

Cheers,
Leif

[4.0.0] Consider renaming executable and library

Michael Osipov — Sun, 08 Mar 2020 11:28:26 -0000

Please consider giving all binaries better names in Version 4.0.0. The sole name wrapper isn't really helpful and way generic. Consider making it jsw, jsw.jar, libjsw.so, etc.