Oh dear, thanx Stephane for the clarifications.. I completely forgot that EAR i built were EJB3 based, where i didnt have an ejb artifact as i can deploy ejbs as jars
thanks for pointing that out..... regards marco On 2/6/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
Hi, On 2/6/07, Manos Batsis <[EMAIL PROTECTED]> wrote: > > Hey Marco, > > Thanks for your email. > > Quoting Marco Mistroni <[EMAIL PROTECTED]>: > > any particular reason for not using maven-ear-plugin, since it will > > generate manifest classpath entries based on dependencies of your > > projects? > Even if you do this, it won't work AFAIK since it's not part of the spec. The way to define dependencies between an EJB module and third-party libs is to define a manifest for the *EJB* module. Does this actually work? On which app server? > * Will the WAR and EJB-JAR obey the EAR manifest? I used to create the > manifest for those modules with Ant for this structure to work. I am pretty sure it won't work and this way of working is not compliant anyway. Back to your original question, this is an interesting use case. Why don't you generate the manifest when you actually build your EJB modules? Maven can do this for your (see the archive settings). Regards, Stéphane > > > Many thanks, > > Manos > > > > > hth > > marco > > > > On 2/6/07, Manos Batsis <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > Hello, > > > > > > Back in my Ant-based projects i used the pathconvert to generate > > > manifest files from myruntime.classpathref. I also filtered all > > those > > > jars out of my WARs/WEB-INF/lib and put them in the EAR/lib, where > > > (thanks to the manifests) both EJBs and WAR classes could access > > them, > > > avoiding duplication of library JARs. > > > > > > I'm getting ready to port the same logic through the antrun plugin, > > then > > > use exclusions and what not to finally end up with the same > > structure > > > and was wondering if there is a better way to do this. > > > > > > Thanks in advance, > > > > > > Manos > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
