Sorry Jeff, i m little bit lost...
i think i lost the original thread..
as far as i remember, your problem is that you have shared jars that end up
in your .ear and you don't want that..correct?
But my resulting ear file has extra jars in its root (eg
j2ee-1.3.0.jar ,log4j-1.2.13.jar) , together with my jportal-1.0.0.war
if you don' t need those extra jars, then put <scope>provided</scope>
if you have jars (such as spring) which are shared by different project, is
it a problem to put those classes as utility classes in your .ear rather
than putting them inside .war?
.war project will still be able to see them......
hth
marco.
On 10/20/06, Jeff Mutonho <[EMAIL PROTECTED]> wrote:
On 10/19/06, Marco Mistroni <[EMAIL PROTECTED]> wrote:
> hi,
> try to use <scope>provided</scope> for those jars
>
> hth
> marco
>
Ok I understand, but my problem is that some of these shared jars ,eg
the spring one is used by all the sub-modules during compilation , but
only need to be bundled in the war only.I'f I use
<scope>provided</scope> in the top level pom , then they will not be
bundled with the war file.At the same time I am trying to avoid
duplication of , eg
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>1.2.3</version>
<scope>test</scope>
</dependency>
in all the sub modules.
Jeff Mutonho
GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
