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]
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:
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
On Sat, 2007-06-30 at 11:12 +0930, Barrie Treloar wrote:
I'm excluding it because EasyConf specifies a different version and I
need to override it.
Doesn't just pinning the version in dependencyManagement in such
situations work? It should not be necessary to exclude the wrong
version. However,
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
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
