A JAR in a classpath is a JAR in a classpath, no? I always assumed that when people pre-loaded runtime libraries it was out of a desire to minimize artifact size and/or optimize reusability within the JVM (thus by inference, minimize risk of the PermGenblowing up).
In my view, a project *should* be as self contained as possible, except for a precious few optimization aspects like pooling of connections, sharing of cache etc. Few things are as daunting as trying to get a project to run, which is dependent on libraries and settings only the original developer knows about - and has likely forgotten. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/6MhOVhqXmUMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
