Re: Convention for location of jar files
Knute Johnson <eternal@knutejohnson.com> writes:
C:\Users\Knute Johnson\com\knutejohnson\customer\packagename\...
Yes, but what about third-party libraries like Apache Commons?
In the best case, several different Java applications who use
the same Apache Commons library access them in one single place.
This would implement DRY (Don't repeat yourself): The
same library is not stored several times with different
applications.
Assume there is a security warning: An Apache Commons Library
contains a security issue and should be replaced by the new
version. When there is a system-wide location for that library
that is used by all applications, the administrator would
update that library and rest. Otherwise, he'd need to check
every Java application for possible appearances of that
library (possibly nested or contained in some JAR archive,
that might even be contained in some other archive.)
Similar to package names, libraries and applications should
have a world-wide unique identifier, then there should be
calls to install a certain version of a library or application
?in the system? or to obtain it from the system. This API even
could download from Maven repositories, but should default
to ask the user before establishing contact to any remote server
and transparently show to the use which remote and local
locations it accesses.