On 6/23/06, Mike Perham <[EMAIL PROTECTED]> wrote:
Yep, I just ran into this also. I have a module which has [1.1.0,) and 1.1.0 and 1.1.1-SNAPSHOT in my local repo. I can't release the module. It basically makes dependency ranges unusable for us. I'm unclear who's at fault here (the release plugin, maven's dependency resolution alogrithm, etc) but it seems like release plugin should ignore resolved SNAPSHOTs where that dependency was specified with a range. Anyone else have any comments?
I'm a bit disappointed, anyone has successful experiences with version ranges? [Akbarr]
