Subdeployment manifest locations should not be added if they are in the parent context -------------------------------------------------------------------------------------- Key: JBDEPLOY-59 URL: http://jira.jboss.com/jira/browse/JBDEPLOY-59 Project: JBoss Deployers Issue Type: Bug Components: deployer Reporter: Adrian Brock Fix For: JBDEPLOY-2.0.0.CR1 When AbstractStructureDeployer processes the manifest for a subdeployment context, it includes entries that are already included in the parent context within the classpath of . e.g. top-level.ear/utility.jar top-level.ear/sub-deployment.war If sub-deployment.war contains a manifest entry with Class-Path: utility.jar This should not be included because it is already in the classpath as part of top-level.ear (assuming top-level.ear lists it in the appliaction.xml, if it didn't it should include it in the cflasspath of subdeployment.war). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira