maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barrie Treloar" <>
Subject Re: dependency:analyze incorrectly using excludes from DepMgt section.
Date Sat, 30 Jun 2007 01:42:17 GMT
> > I only excluded javax.servlet from EasyConf and not commons-logging,
> > so I shouldn't be getting this error.
> 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.

I'm excluding it because EasyConf specifies a different version and I
need to override it.

I have no idea why commons-logging wants javax.servlet. So I might try
excluding it as well.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message