🚀 go-pugleaf

"Joi Ellis [TeamB]" <joi@aravox.com> writes:

> Ok, now I'm confused.  That page is talking about JDK extensions.
> Extensions are packaged in a single jar for easy installation and
> security.  There's nothing in there at all about java packages.

Java packages that represent "extensions"/libraries your app depends
on (say, classes12.zip for Oracle JDBC) should be addressed via
"Class-Path" for purposes of allowing "java -jar" type invocation,
which doesn't use -classpath or the env. variable CLASSPATH.

The alternatives are either to ship the packages as part of the JAR
file (which is akin to static linking in C and perhaps against the
license for the library) or place the jars in the lib/ext directory of
the JRE.

This is relevant to how the JBuilder Archive Builder wizard constructs
the manifest file for libraries with "Exclude all" option. You can
tell it to create the manifest into the project, edit that by hand and
change the archive node to use the edited manifest, though.