Thanks Prasad. I'm not yet sure if we are picking up *unnecessary jars*
(but it does look suspicious). It appears that we pick these up in our
current build. It's just a matter of where we get them from. I'd like
to first get things working by picking up just the jar that I need
(JSTL) from java.net and check to see if in fact we are picking up other
jars that are not necessary
(javax\servlet\servlet-api\2.4\servlet-api-2.4.jar in this case).
Joe
Prasad Kashyap wrote:
I don't think the search order will solve your problem because the
different spec jars are being picked up as transitive dependencies. So
no matter what the search order, those aritfacts will be picked up
since they are listed explicitly as dependencies of your dependencies.
I believe you should use dependency exclusion to prevent picking spec
jars you don't need.
Cheers
Prasad
On 10/20/06, Joe Bohn <[EMAIL PROTECTED]> wrote:
On my local image I added a new repo to the root pom.xml so that I could
pick up the Glassfish JSTL jar. What I discovered is that this resulted
in java.net getting placed before the apache repo in the search order
and therefore I'm picking up different jars (specs) from java.net (which
is breaking me because they are built on 1.5).
So, the question is .... How can I include a new repo but at the end of
the search order? There is a comment in the root POM about genesis
being the place where the other repos are specified. Do I have to add
my repo to Genesis to get it last in the order instead of first?
Thanks,
Joe
