PM35243: Utility JAR files are imported as application client projects when importing an EAR version 5 or 6

APAR status

• Closed as program error.

Error description

• When an EAR version 5 or 6 is imported the utility JAR files
  inside the EAR are imported as application client projects if
  they have a Main-Class specified in MANIFEST.MF.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an EAR version 5 or 6 is imported the utility JAR files
  inside the EAR are imported as application client projects
  if they have a Main-Class specified in MANIFEST.MF.
  

Problem conclusion

• All JAR files located in the EAR library directory will be
  imported as Utility JARs. JAR files located in other
  directory different from the EAR library directory will be
  imported as application client projects if they have a
  Main-Class specified in MANIFEST.MF.
  
  The EAR library directory can be specified in the deployment
  descriptor of the EAR (application.xml). If it is not
  specified or if the EAR does not have deployment descriptor
  then the lib directory is used as the EAR library directory.
  
  This issue is fixed in Rational Application Developer
  Version 8.0.3.
  

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

• R753 PSN

     UP