The following issue has been updated: Updater: Dain Sundstrom (mailto:dain@coredevelopers.net) Date: Wed, 8 Sep 2004 12:26 PM Changes: summary changed from EJB Class-Path entries are not found during deployment to Ear, war, ejb-jar, and rar manifest Class-Path entries are ignored by configuration builders description changed from I have an EAR which contains an EJB-JAR which has a Class-Path entry to another library jar. During deployment I get a NoClassDefFoundError for classes that are in that library jar as it can't find it in the temp directory. Trying to use a in the EAR doesn't help - are these supported? to I have an EAR which contains an EJB-JAR which has a Class-Path entry to another library jar. During deployment I get a NoClassDefFoundError for classes that are in that library jar as it can't find it in the temp directory. Trying to use a in the EAR doesn't help - are these supported? Version changed to 1.0-M1 Version changed from 1.0-M2 --------------------------------------------------------------------- For a full history of the issue, see: http://issues.apache.org/jira/browse/GERONIMO-249?page=history --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/GERONIMO-249 Here is an overview of the issue: --------------------------------------------------------------------- Key: GERONIMO-249 Summary: Ear, war, ejb-jar, and rar manifest Class-Path entries are ignored by configuration builders Type: Bug Status: Unassigned Priority: Major Project: Apache Geronimo Components: deployment Versions: 1.0-M1 Assignee: Reporter: Simon Godik Created: Mon, 21 Jun 2004 11:20 PM Updated: Wed, 8 Sep 2004 12:26 PM Description: I have an EAR which contains an EJB-JAR which has a Class-Path entry to another library jar. During deployment I get a NoClassDefFoundError for classes that are in that library jar as it can't find it in the temp directory. Trying to use a in the EAR doesn't help - are these supported? --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira