Thanks for the info, that helped a lot.
Enrique
[EMAIL PROTECTED] wrote on 11/14/2006 03:17:07 PM:
> What I do is put the utility jar in my dependency for the war as compile.
> Then I put an exclude in the pom for the war that tells it to leave out
the
> jar and not put it into the war. The clas
yne Fay <[EMAIL PROTECTED]> wrote:
> >
> > Incorrect, Lee M. responded to you earlier...
> >
> > -- Forwarded message --
> > From: Lee Meador <[EMAIL PROTECTED]>
> > Date: Nov 14, 2006 3:17 PM
> > Subject: Re: Maven dependency question
> > To:
On 11/15/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
Incorrect, Lee M. responded to you earlier...
-- Forwarded message --
From: Lee Meador <[EMAIL PROTECTED]>
Date: Nov 14, 2006 3:17 PM
Subject: Re: Maven dependency question
To: Maven Users List
What I do is put
Incorrect, Lee M. responded to you earlier...
-- Forwarded message --
From: Lee Meador <[EMAIL PROTECTED]>
Date: Nov 14, 2006 3:17 PM
Subject: Re: Maven dependency question
To: Maven Users List
What I do is put the utility jar in my dependency for the war as compile.
Subject
Maven dependency question
Hi folks,
We have a J2EE application project (ear) which contains one Web project
(war), one EJB project and one utilities java project.
The war and EJB jar projects depends from the same utilities project.
We included the WEB, EJB and utilities p
What I do is put the utility jar in my dependency for the war as compile.
Then I put an exclude in the pom for the war that tells it to leave out the
jar and not put it into the war. The classloader for your application server
should cause the war to have access to the jar since it is in the ejb j
Hi folks,
We have a J2EE application project (ear) which contains one Web project
(war), one EJB project and one utilities java project.
The war and EJB jar projects depends from the same utilities project.
We included the WEB, EJB and utilities projects as dependencies into the
ear pom file, so
