I'm hoping someone has seen this before. My war has a dependency on an ejb-client jar, and I want the ejb-client placed inside the ear not the war. I am using the <optional>true</optional> tag on the dependency in the war so that the manifest gets updated to have the reference to the ejb-client jar, but that the ejb-client is not placed in the web-inf\lib of the war.
When I do a Maven install from my war project and then the ear project all is fine. When I build from the parent it is placing the ejb-client jar inside the web-inf\lib of my war. Subsequently at execution time, the code breaks because the war classpath does not have visibility into the ear classpath to find the ejb jar. Has anyone seen this difference ehen building from the parent and know how to get around it? We are using a product called TPM to kick off the Maven builds and it always does so from the parent. Thanks for your help! Amy --------------------------------------------------------- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. ---------------------------------------------------------
