>You can merger two jar files into one using this command
My end-goal is to distribute a single .jar executable that is immediately runnable, with no installation required (except Java, of course). However, if the >bes...
rwilson352 wrote:Are they going to use your database? Because if your users are not smart enough to set up a env var then there is absolutely no way they are going to set up a database.
The program (obviously) requires a JDBC driver to be installed in order for it to work. On my developer machine, I obviously have the driver installed (and thus the program runs fine on my computer). The driver itself has no installer, it is simply a .jar file that needs to be pointed to by the environment variables. However, I do not want the user to have to change their environment variables in order to get my program to run (sorry, but asking a non-computer person to change their environment variables is asking for trouble, imo).
Is there any way to "wrap" the driver within the .jar executable that I intend to distribute? I have looked online, but I'm pretty sure I'm lacking the proper vocabulary to describe my issue well enough for google to help.Yes. You must create the manifest so it references the driver. Many threads have discussed it on the JDBC forum. Following keywords in google seemed promising to me.
rwilson352 wrote:Then learn about installers.
And, for future reference... It's not about "are they smart enough" to set up an environment variable, but that I have never ever ever had to do such a thing for any software other than development-oriented software (JDK, JDBC drivers, etc), and it just makes me look incompetent and unable if I force the user to do a very complex installation for such a small program. They are not software people and the essence of abstraction is to keep the user focused on relevant tasks and information. The appearance of professionalism and intelligence is crucial to keeping the work coming in my direction.