[ http://issues.apache.org/jira/browse/GERONIMO-2125?page=comments#action_12419936 ]
Mario Ruebsam commented on GERONIMO-2125: ----------------------------------------- I analyzed my problem a bit further with your example. In 1.0 you could add one or more utility jars to the ear. If one of these files depend on another jar, you don't have to add a classpath entry into the manifest file of this utility jar. The entry must only exist in the war or the ejb-jar referencing the jar on top of the other utlity jars. In 1.1 it works only if every utility jar contain a classpath entry to the other used jar's. Extending your example with two new jars: web.war depends on tools.jar in the ear root, tools.jar depends on found.jar also in the ear root in 1.0 you need a classpath entry in web.war too tools.jar in 1.1 you need a classpath entry in web.war too tools.jar and an entry in tools.jar too found.jar If the new behaviour in 1.1 is correct (I'm not familiar with the spec), then it is difficult to include 3rd party jars which depend on each other but doesn't have a correct classpath entry. The only way then is to use the repository and dependecies or path the manifest in the 3rd party jars. > Classpath entries in the web app archive META-INF/MANIFEST.MF are not added > to the wep app class path > ----------------------------------------------------------------------------------------------------- > > Key: GERONIMO-2125 > URL: http://issues.apache.org/jira/browse/GERONIMO-2125 > Project: Geronimo > Type: Bug > Security: public(Regular issues) > Components: deployment > Versions: 1.1 > Environment: 1.1 release > Reporter: Mario Ruebsam > Assignee: David Jencks > Priority: Blocker > Fix For: 1.2, 1.1.1 > Attachments: ear-1.0-SNAPSHOT.ear, manifestcp-itest.jar > > A working EAR for Geronimo 1.0 with this structure: > app.ear/ > app.jar > cpa.jar > found.jar > webclient.war > The util JARs are referenced from the webclient.war/META-INF/MANIFEST.MF > Class-Path: app.jar cpa.jar found.jar > Deployment of this EAR in G 1.1-rc1 result in ClassNotFoundExceptions because > of the missing classes in the JARs which are not found. > Putting the JARs into the webclient.war/WEB-INF/lib worked. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
