PM64691: A JAR file in the root of an EAR project does not show up in the EAR libraries of a project in the EAR library directory

Rational Application Developer for WebSphere Software 8.5.1
Rational Application Developer Standard Edition, Version 8.0.4.2

APAR status

• Closed as program error.

Error description

• Abstract:
  
  A JAR file in the root of an Enterprise Application project does
  not show up in the EAR libraries classpath container of a
  project in the EAR library directory
  
  Problem:
  
  When a JAR file is added to the root of an Enterprise
  Application project, it does not show up under the 'EAR
  libraries' classpath container for a Utility Java project
  associated with that same Enterprise Application project, which
  is located in the EAR library directory. The MANIFEST.MF of the
  Utility project has an entry for the jar, of the form
  ../file.jar.  As a result, any code in the Utility project
  referencing classes in the JAR file will fail to compile.
  
  Local fix:
  
  To work around this issue you can manually add the JAR to the
  build path of the Utility project to eliminate the compilation
  errors.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a JAR file is added to the root of an Enterprise
  Application project, it does not show up under the 'EAR
  libraries'  classpath container for a Utility Java project
  associated with that same Enterprise Application project,
  which is located in the EAR library directory.
  
  The MANIFEST.MF of the Utility project has an entry for the
  jar, of the form ../file.jar.  The prefix ../ is necessary
  because the entries in the MANIFEST.MF must be relative to
  the location of the JAR that owns the MANIFEST.MF.
  
  As a result, any code in the Utility project referencing
  classes in the JAR file will fail to compile.
  

Problem conclusion

• The fix for this APAR is included in Rational Application
  Developer v8.0.4.2.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL APP DEV WI

• Fixed component ID

  5724J1901

Applicable component levels

• R803 PSN

     UP