# Standard Enterprise Application Project Properties Dialog Box: Libraries

The Libraries page lets you define the JARs, folders, libraries, and projects that are added to the runtime classpath of the enterprise application. The libraries that you add are then available to all the modules in the project.

In the Libraries page, you can set the following properties:

Element | Description
--- | ---
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 Ant Library Manager.
Embedded Classpath Elements | You use this page to specify any projects, subprojects or libraries not listed in the Packaging page that you want the IDE to include in the classpath of the enterprise application when you debug the application. You use the Packaging page to specify the libraries that are packaged in the EAR archive when you build your enterprise application. However, your enterprise application may require elements such as special libraries (such as JDBC drivers or additional libraries), JARs or other projects that are not listed in the Packaging page. If you want to step through these elements when debugging the application, you need to explicitly specify the elements in the Libraries page. For example, the Packaging page may specify that your WAR archive will be bundled in the EAR archive. However, the web application may require a subproject that is not packaged in the WAR archive but which will be copied to the EAR archive when you build the enterprise application. If you want to be able to step through the subproject when debugging the enterprise application, you need to explicitly specify the subproject in the Libraries page. Use the buttons to add JAR files, projects or libraries to the classpath.

Related Topics

Developing Applications with NetBeans IDE,

Developing Applications with NetBeans IDE,

Developing Applications with NetBeans IDE,

Developing Applications with NetBeans IDE,

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.