There
are two pieces to managing the JAR files that a project requires:
the SAS Versioned Jar Repository, and the project's SAS Repository.
The SAS Versioned Jar
Repository is a common storage location for all the JAR files that
are supplied by the installed SAS products. This includes some third-party
JAR files. This repository is incrementally updated as SAS products
are installed.
A project's SAS
Repository is a configurable classpath container that is added to
the Java build path of all SAS projects to provide access to the JAR
files in the SAS Versioned Jar Repository. The SAS Repository determines
which SAS JAR files need to be included in a project’s build
path. It can also determine any JAR file dependencies and automatically
include those dependencies in the project’s Java build path.
This ability means that you need to specify only the primary JAR files
that a SAS project requires, the dependencies are handled for you.
When necessary, you
can bypass the SAS Repository automation and specify exactly which
JAR files, and which versions of each JAR file, to include. This flexibility
enables you to manage JAR file dependencies on a per-project basis
without disrupting past development, and contributes to a smaller
distribution footprint.
If you want to add to
the project a JAR file that is not available in the SAS Versioned
Jar Repository, open the project properties, select
Java
Build Path, and use one of the mechanisms that does not
involve editing the SAS Repository on the
Libraries tab.
You are responsible for adding any JAR file dependencies.