23

Are there any industry standard conventions for naming jar files?

Greg Hewgill
  • 951,095
  • 183
  • 1,149
  • 1,285
Ron Tuffin
  • 53,859
  • 24
  • 66
  • 78

2 Answers2

26

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)

SkyWalker
  • 28,384
  • 14
  • 74
  • 132
Ron Tuffin
  • 53,859
  • 24
  • 66
  • 78
2

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

blacktide
  • 10,654
  • 8
  • 33
  • 53
wdk
  • 373
  • 2
  • 8