The Libraries panel enables you to register libraries on a project's various
classpaths as well as set the target Java platform against which all source
files are compiled and run. You open the Enterprise Application Client Properties
dialog box by right-clicking any application client node and choosing Properties.
You can configure the following project classpaths:
Compilation classpath
Runtime classpath
JUnit test compilation classpath
JUnit test runtime classpath
Use the buttons on the right side of the panel to add, remove,
and change the order of classpath elements. You can add any of the following:
JAR file. A Java archive file somewhere on your system.
Library. A collection
of binary files, source files, and Javadoc files.
Project. The build
output, source files, and Javadoc files of another IDE project.
Notes:
If a JAR file with attached souce code and Javadoc documentation is registered
with a project as a member of a Java Class Library, you can simply
add the JAR file to the classpath and the IDE finds the Javadoc documentation
and source code automatically.
Adding a Java Class Library rather than a regular JAR file also makes it easier for other developers
you share the project with to fix broken references to Javadoc documentation
and source code.
Adding a
to the classpath of a standard project does nothing
unless you also declare the free-form project's build outputs in the Output
page of its Project Properties dialog box.
By default, the project's compiled sources and everything on the compilation
classpath are also on the runtime classpath.
By default, the project's compiled test files and everything on the tests'
compilation classpath are also on the test runtime classpath.