On Fri, 2007-06-29 at 21:26 +0930, Barrie Treloar wrote: > On 6/29/07, Heinrich Nirschl <[EMAIL PROTECTED]> wrote: > > On Thu, 2007-06-28 at 10:20 +0930, Barrie Treloar wrote: > > > When I run dependency:analyze on my module I get: > > > > > > [INFO] Found Resolved Dependency / DependencyManagement mismatches: > > > [INFO] Ignoring Direct Dependencies. > > > [INFO] javax.servlet:servlet-api:jar was excluded in DepMgt, but > > > version 2.3 has been found in the dependency tree. > > > > > > mvn site's Dependency Tree: > > > org.springframework:spring-beans:jar > > > * commons-logging:commons-logging:jar > > > o logkit:logkit:jar > > > o avalon-framework:avalon-framework:jar > > > o javax.servlet:servlet-api:jar > > > > > > > This is why servlet-api was pulled in. You seem to have a dependency on > > spring which in turn uses commons-logging and commons-logging brings in > > servlet-api. > > > > I always add the exclusions you specified for easyconf also to all the > > spring modules. > > Look more closely at the error > > > [INFO] javax.servlet:servlet-api:jar was excluded in DepMgt, but > > > version 2.3 has been found in the dependency tree. > > 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
