Try extracting all your dependencies (with versions) and move them
into a <dependencyManagement/> section in a shared parent pom. Then
remove the <version/> nodes specified in the dependencies in all the
children poms.
Wayne
On 4/6/07, Tommy Knowlton <[EMAIL PROTECTED]> wrote:
Hello,
My project team has got on the order of 30 projects that contribute to
a single webapp. Most of the projects produce
<packaging>jar</packaging> artifacts, that go into the webapp's
WEB-INF/lib.
The problem I'm having is inconsistency with how Maven resolves (and
names) versioned artifacts... Within WEB-INF/lib, I see things like:
project-a-1.0.0-20070406.175320-144.jar
project-b-1.0.0-SNAPSHOT.jar
Mind you, both projects A and B are at
<version>1.0.0-SNAPSHOT</version> both within their own POMs as well
as in the <dependencies/> of dependent projects' POMs.
It seems like the difference in naming has to do with how directly the
webapp depends on the given artifact: direct dependencies appear to
get the "-SNAPSHOT" naming style, while transitive dependencies appear
to get the "-${DATE}.${TIME}-${BUILDNUM}" style.
The real problem appears when a (direct) dependency is also a
transitive dependency. I've seen numerous instances where two copies
(differing only by name) of the same jar end up in WEB-INF/lib.
Has anybody else seen anything like this? Can somebody help me figure
out what I'm doing wrong? I don't yet have a "minimal" example to
demonstrate the problem, and I'm willing to believe that it's the
large complex nature of my project that is contributing, but I don't
yet know where to start looking for the cause.
Thanks,
--
Tommy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
