geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Hogstrom <>
Subject Re: We may need to rethink unversioned dependencies among server plans...
Date Thu, 20 Apr 2006 01:54:49 GMT
This is behaving as designed isn't it?  I would expect the highest level version to be selected
the absence of a restriction (another dependency indicated that it required 1.1-SNAPSHOT)
or a 
specific dependency (some dependency indicated it needed naming-1.1-SNAPSHOT).

Does this sound right?

Aaron Mulder wrote:
> So I'm having a build problem.
> The root cause appears to be that my local Maven repo has both
> 1.1-SNAPSHOT and 1.2-SNAPSHOT artifacts.  One of the server artifacts
> (say, j2ee-system) has a dependency on another (say, rmi-naming), and
> that dependency has no version.
> So when the packaging plugin packages j2ee-system, it asks the
> repository for a matching rmi-naming, and gets rmi-naming/1.2-SNAPSHOT
> instead of rmi-naming/1.1-SNAPSHOT
> I'm not sure what we can do about this.  I'll think about it a bit.
> Thanks,
>     Aaron

View raw message