ZIP extension is more convenient to open archive than
that is true for GUI, Windows GUI. When you work with CLI zip/unzip, "jar" extension is not a problem and "jar" extension clearly express that this is java JAR file. Some shells with autocompletion will not offer "jdbssql.zip after "java -jar" because they offer only ".jar" files (you can try bash at Ubuntu).
In most cases user don't need to extract/modify jar archives. Unfortuentay, design of jdbcsql requires modification of jar archive to add/update/change JDBC driver. I created other ticket to request aditional parametrs to support for external JDBC driver; that will address problem with zip/jar archive dilema.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ZIP extension is more convenient to open archive than jar
that is true for GUI, Windows GUI. When you work with CLI zip/unzip, "jar" extension is not a problem and "jar" extension clearly express that this is java JAR file. Some shells with autocompletion will not offer "jdbssql.zip after "java -jar" because they offer only ".jar" files (you can try bash at Ubuntu).
In most cases user don't need to extract/modify jar archives. Unfortuentay, design of jdbcsql requires modification of jar archive to add/update/change JDBC driver. I created other ticket to request aditional parametrs to support for external JDBC driver; that will address problem with zip/jar archive dilema.
Major idea is all files to be encapsulated in one jar/zip.
It's ready for deploy.