[8.5.5.6 or later]

Customizing the Liberty class path container

You can customize the contents of the Liberty class path container by excluding third-party API libraries, IBM® API libraries, and unrecognized content in your Java™ EE project.

Before you begin

Important: Applicable to Liberty, Liberty Core
If you do not see the Java EE icon, J2EE perspective icon, in the workspace, you need to switch to the Java EE perspective.

About this task

Projects that target WebSphere® Application Server Liberty automatically have the Liberty library added to their class path. This library contains the API classes from the JAR files that are included in the Liberty server. The contents of this library depend on the facets that are installed in the project. For example, depending upon which JPA facets are installed, the library includes or excludes certain JAR files to avoid conflicts:

  • If the project has the JPA 2.1 facet, the library includes the JAR files for JPA 2.1 and excludes the JAR files for JPA 2.0.
  • If the project has the JPA 2.0 facet, the library includes the JAR files for JPA 2.0 and excludes the JAR files for JPA 2.1.
  • If the project does not have the JPA facet, the library includes the JAR files for JPA 2.1 and excludes the JAR files from JPA 2.0.

You can alter what is included by default in the class path container by excluding third-party API libraries, IBM API libraries, and unrecognized content.

Procedure

  1. Right-click on the project, and select Properties > Liberty.
  2. Select the API that you want to exclude.
  3. Click OK.
Icon that indicates the type of topic Task topic
Timestamp icon Last updated: July 17, 2017 21:58

File name: tcustomclasspath.html