Re: Using jar inside a jar
On 1/23/2015 10:46 AM, Nigel Wade wrote:
On 23/01/15 12:12, Joerg Meier wrote:
On Fri, 23 Jan 2015 11:10:35 +0000, Nigel Wade wrote:
I'm not a fan of the "big jar" concept. I much prefer to keep
libraries in separate jar's. If a library class gets
updated it's only need to update a single library jar, rather than
every "big jar" which contains that class.
Different areas, I'd say. For end users you almost never would want
them to
update libraries on their own, unless your end users are developers.
Why not? End user, or system admin. I'd still not supply a "big bundled
jar" unless there was a specific requirement to do so.
When you get updates from Microsoft do you get a few small patched
libraries, or GB's of statically linked applications each time?
My plain-vanilla Windows 7 system has ten count them ten
different versions of "Microsoft Visual C++ 20xx Redistributable"
installed. Why do you suppose Redmond ships so many different
editions of the same library, instead of just updating the latest?
In other words: If you develop an application using external
libraries A,B,C, you will at some point test it with A 1.2.0-5,
B 2.1.1-18, and C 1.9.12-3. Will your application still work
properly with updated A 1.2.1-0, B2.1.1-21, and C 2.0.1-1? To
get around issues of version skew, might you consider bundling
the tested versions of A,B,C along with your application as
opposed to telling the end user to install A,B,C versions in
combinations you've not tried?
Welcome to the joys of "component architecture" ...
--
esosman@comcast-dot-net.invalid
"Don't be afraid of work. Make work afraid of you." -- TLM