Jason van Zyl wrote:
Frankly, even if version ranges worked as above I'd still probably
not use them during a build simply because I want to specify exactly
what is used in the build. However, it would be great to know that
multiple projects have dependencies on incompatible versions of the
same thing. It would also be great to have reports that indicate
which dependencies could be safely upgraded.
The approach above goes in this direction - it might give some
guarantees. But not too strong - we cannot test behavioral
compatibility.
Not without some decent integration tests no. But you have a pretty
good chance with good ITs. We catch lots of shit that compiles, but
bombs in our ITs.
I believe Oleg meant behavior incompatibilities of third party
artifacts, not Maven. Maven's ITs can't be expected to detect problems
with other projects.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
