Are there any industry standard conventions for naming jar files?
File naming best practices:Avoid special characters or spaces in a file name. Use capitals and underscores instead of periods or spaces or slashes. Use date format ISO 8601: YYYYMMDD. Include a version number (Creamer et al.
The jar file name does not matter.
In Java, the java file name should be always the same as a public class name. While writing a java program first it is saved as a ". java" file, when it is compiled it forms byte code which is a ".
I have been using
*Informative*-*name*-*M*.*m*.*b*.jar
Where:
M = major version number
(changed when backward compatibility is not necessarily maintained)
m = minor version number
(feature additions etc)
b = build number
(for releases containing bug fixes)
If your jar is used for JEE then these guidelines apply:
The module name is used as the EJB archive name. By default, the module name should be based on the package name and should be written in all-lowercase ASCII letters. In case of conflict, the module name should be a more specific version (including other part of the package name):
EJB archive: -ejb.jar
EJB client archive: -ejb-client.jar
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With