You open this dialog box by right-clicking any and choosing Properties. The Libraries page lets you set up the
libraries that the project contains on its classpath.
Java Platform. You can use the Java Platform drop-down list to set the specific JDK installation
that the IDE uses to compile and run your project. The IDE adds the selected
platform's libraries to the classpath and uses the platform's executables (such
as javac and java) to run and build the project. The default
platform for all projects is the platform on which the IDE is running. You can
register additional platforms and attach Javadoc and source files to a platform
by clicking Manage Platforms.
Libraries Folder. To make it easier to
share libraries among different
users and projects, you can set a folder to hold those libraries (or references to
those libraries). You can create a new folder or specify an existing folder that
already contains copies of the libraries on which your project depends.
To specify the folder, click Browse. If there is already a libraries folder, a
file chooser opens. If there is not a libraries folder, the New Libraries wizard opens.
In the New Libraries wizard, you set a libraries folder and then specify how to reference
each library. The simplest case is to have the libraries copied to that folder.
You can also refer to the libraries in their existing location
(with a relative path or an absolute path). If you have specified an existing folder,
you also have the option of using copies of libraries that are already in that folder
instead of the copies that are contained in the IDE's Library Manager.
Each standard EJB module project maintains a separate classpath for compilation,
compiling tests, and running tests. Use the buttons on the right of the dialog
box to add, remove, and change the order of classpath elements. You can add
any of the following:
JAR file or folder. A JAR file or folder containing compiled class
files and other resources.
Library.
A collection of JAR files, source code, and Javadoc that has been registered
in the Library Manager.
Project. The build output, source
files, and Javadoc files of another IDE project.
Notes:
By default, all libraries on the compilation classpath are packaged with
the EJB JAR file for deployment.
By default, all items that are on the classpath are packaged in the WAR file.
Deselect the Package checkbox for each classpath item that you want to exclude from the JAR file.
If the EJB module is deployed as a stand-alone
module, the IDE includes the JAR files in the EJB module JAR file. If the
EJB module is deployed as part of an enterprise application, the IDE includes
the JAR files in the application EAR file.
If a JAR file is registered in the Library Manager and has attached source
code and Javadoc documentation, you can just add the JAR file to the classpath
and the IDE finds the Javadoc documentation and source code automatically.
You should use the Add Library button if you want to add a library that contains
several JAR files. Adding a library that is managed in the Library Manager
also makes it easier for other developers with which you share the project
to fix broken references to Javadoc documentation and source code.
Adding a to the classpath of a standard project does nothing unless you have
declared the free-form project's build outputs in the Output page of its Project
Properties dialog box.