Re: dependency:analyze incorrectly using excludes from DepMgtsection.

[Barrie Treloar <ba...@gmail.com>]

On 6/30/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >Ah, now I see what you mean. This does indeed look strange, especially
> >the wording of the message. On the other hand, it is just an INFO and
> >not a WARNING like the other problems found by the dependency:analyze
> >goal. I don't know if this behavior is intended. The message may be
> even
> >useful, because there may be something wrong in the project if a
> certain
> >dependency is excluded from one module but pulled in by another. If I
> >exclude it once it is very likely that I don't want it in my module at
> >all.
>
> Hi, this is how it was intended to work. It's intentionally looking for
> anything you excluded somewhere to see if it crept back in through
> another avenue. See here: http://jira.codehaus.org/browse/MDEP-76

Hmm.

I'll have to think more on this.

At the moment, I don't think excluding it from one plugin and then
getting it from another is an error, but I'm not sure why I think that
right now.

I know EasyConf's plugin is junk. I am at home trying to remember
stuff I should be checking at work... but I think EasyConf is not
specifying provided for javax.servlet and thus I am excluding it for
that reason.

I would have to thought spring would be defining the right dependency details.

I know I had to do something with log4j and one of the plugins a while
ago because of a bug somewhere.  I wonder if I should be overriding
the dependency with the correct values instead of just excluding it...

I will ponder this some more.
Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org