I believe this is done in CVS already.
--
dIon Gillard, Multitask Consulting
"Teemu Hiltunen" <[EMAIL PROTECTED]> wrote on 04/03/2004 10:05:23 PM:
> Greetings!
>
> We're trying to create an ear with some ejb-modules and a war-module.
The
> ejb-modules and war uses some common jars. I was wondering whether it is
> even legal to put these commons jars into ear root without the need to
put
> them each into an ejb-module and war-module? And if it is legal (should
be)
> then the Maven ear-plugin should be modified to include jars without
making
> a <module>-element into application.xml - because the common jars are
not
> application client jars. We have some problems with Oracle AS when
deploying
> an ear where all the correct jars are inside each ejb or war module.
>
> I modified the ear-plugins (version 1.3) plugin.jelly file:
>
>
<!--==================================================================-->
> <!-- Creates ear descriptor - application.xml file -->
>
<!--==================================================================-->
> <goal name="ear:generate-ear-descriptor" description="Generates the
ear
> descriptor">
> ...
> <j:when test="${dep.type=='jar'} and
> ${dep.getProperty('ear.appxml.include')=='true'">
> ...
>
> and added into project.xml in common jars (log4j for example):
>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.8</version>
> <type>jar</type>
> <url />
> <properties>
> <ear.bundle>true</ear.bundle>
> <ear.appxml.include>false</ear.appxml.include>
> </properties>
> </dependency>
>
> Now I can create an ear which doesn't have a <module>-element for
log4j.jar.
>
> So, my question; is it legal to create an ear with "common" jars that
are
> not application-clients and if so should the ear-plugin to be modified
> accordingly?
>
>
> --teemu
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
