Hello,
Another solution is to accept the way the dependency mechanism works and use
CheckStyle or similar to validate dependency model (import control check).
We use the CheckStyle plugin to have the build fail if any checks with
severity error are violated.
One advantage is that it is possible
Hi Thomas,
we are developing a very large project with a layered architecture. We
decided to use Maven (Version 2.0.4) in order to have a good
dependency-management. We are now facing the following problem with
transitive dependencies:
Sorry, but I don't understand what you want Maven to do
Hi Thomas,
first of all it is not necessary to send the same posting to two lists ...
Thomas R. wrote on Friday, March 23, 2007 12:30 PM:
Hello,
we are developing a very large project with a layered
architecture. We decided to use Maven (Version 2.0.4) in
order to have a good
Jörg Schaible wrote on Friday, March 23, 2007 1:59 PM:
[snip]
We use a super POM that defines all used artifacts in a
management section. A project will normal inherit it and
redefine or add customer specific deps. You might add in your
case to all deps a runtime scope, so everyone has to
[INFO] DepMgt : 2.4
[INFO] Resolved: 2.3
[WARNING] Potential problems found in Dependency Management
-Original Message-
From: Jörg Schaible [mailto:[EMAIL PROTECTED]
Sent: Friday, March 23, 2007 9:03 AM
To: Maven Users List
Subject: RE: Problem with Scope of Transitive
