Updating classpath container
As of Rational Application Developer v7.0, the Eclipse WTP 1.5 concept of EAR Libraries and Web Libraries classpath containers was introduced as part of J2EE Module Dependencies.J2EE classpath containers serve to group related classpath information under one classpath entry within the .classpath file (an example is shown later).
If workspace resolution is enabled, m2eclipse will resolve the dependency via the Eclipse workspace.Select this option, and m2eclipse will attempt to download the source artifact from the Maven repository.If it is unable to retrieve this source artifact, you should ask the maintainers of the project in question to upload the appropriate Maven source bundle to the central Maven repository.The upside is that after manually adding the dependency and saving the , the project’s Maven Dependencies container will be automatically updated to include the new dependency.Figure 7.1, “Manually Adding a Dependency to the Project's POM” shows how I added a dependency for into the query field, m2eclipse queries the repository indexes and even shows a version of the artifact that is currently in my local Maven repository.For example, if a WAR project depended on a Java Utility project in the MANIFEST.
MF then there would be a .classpath entry to that Java Utility project. V7 relies on the EAR Libraries classpath container which resolves all projects by reading the MANIFEST. Though v7 has moved away from modifying the .classpath directly the old .classpath entries are still supported, but they are discouraged.
The EAR Libraries or Web App Libraries containers are explicitly added to the .classpath file corresponding to any J2EE/JEE's project property Java Build Path: Libraries [Tab] , hence the projects specified in those containers are implicitly part of the build path.
The workspace Preferences for J2EE (Java EE RAD7.5 ) introduced Classpath containers settings for EAR Libraries classpath containers and Web App Libraries classpath containers as of Rational Application Developer v188.8.131.52, which are checked/set by default.
If a project is configured to resolve dependencies from the workspace, these artifacts do not need to be present in your local repository.
Assume that project-a and project-b are both in the same Eclipse workspace, and that project-a depends on project-b.
A visible example of this change is that an EAR project, as of Rational Application Developer v7.0, has both This the concept of an EAR Library.