Deployment of Depend Jar failure

roygbivens Apr 22, 2003 1:57 AM

I previously used 3.2.0RC4_tomcat-4.1.18 and the deployment of my dependent jars within my ear file were being deployed but with the 3.2.0_tomcat-4.1.24 production release my dependent jars are not being deployed.

My dependent jars are located in the top level of the ear file.

The EARDeployer doesn't seem to be pickin up the jars any longer.

Work around was for me to take the dependent jars out of the ear and just place them in the deploy directory.

Will the EARDeployer automatically deploy jars that are packaged in the Ear?

Do I half to put an entry in my Ears manifest file?

Don't know but it does deploy the war and ejb jar correctly.

1. Re: Deployment of Depend Jar failure

haraldgliebe Apr 22, 2003 2:42 AM (in response to roygbivens)

The behavior was changed as fix for Bug 706213. The EARDeployer now only deploys ejb jars and wars listed in META-INF/application.xml. To add dependent jars to the classpath put them in the manifest classpath of one of the deployed modules.
Actions
2. Re: Deployment of Depend Jar failure

roygbivens Apr 23, 2003 7:12 PM (in response to roygbivens)

Thanks for the reply
Actions

Go to original post