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? I use it already, but i probably not to its full extent. The manifest it creates for the EAR has no classpath entry. Do i have to tell the plugin to create it using jarModule elements for all the runtime dependencies or is there an other way? Even then: * Do i have to manually exclude the deps from my WAR using the plugin? * 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. 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]
