Yes, it can be improved using the new tag. You still may
have to use exclusions in some cases thoguh.
On 10/17/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> From: "Carlos Sanchez" <[EMAIL PROTECTED]>
>
> > Those files are needed to build your application. If you think the pom
> > is wrong and they
From: "Carlos Sanchez" <[EMAIL PROTECTED]>
Those files are needed to build your application. If you think the pom
is wrong and they are actually not needed you can file an issue at
http://jira.codehaus.org/browse/MEV, so you don't need any hack in
your poms.
What about a project like Spring, w
Those files are needed to build your application. If you think the pom
is wrong and they are actually not needed you can file an issue at
http://jira.codehaus.org/browse/MEV, so you don't need any hack in
your poms.
On 10/17/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> From: <[EMAIL PROTECTED]>
>
From: <[EMAIL PROTECTED]>
Is there a way to trun off the dependency checking of maven only for these
javax dependencies?
I don't know if it's the official "right answer" but you can exclude
dependencies... I'm doing it to get rid of the wrong artifact names
(servletapi vs. servlet-api) until
Is there a way to trun off the dependency checking of maven only for these
javax dependencies? Are these really required when I am happy with my
primary jars like hibernate and spring? I understand that the remote repos.
cannot have the sun jars because of license agreements and hence m2 cant
downl
