Is this a bug with strict conflict manager? Or does it not support ranges?

[Robert Macaulay <ro...@gmail.com>]

If I use
defaultConflictManager="strict"

I get this
[ extern | commons-logging | 1.1 ] (needed by [[ extern |
spring-framework | 2.0.2 ], [ ubs | laredo | working@whou0128628 ]])
conflicts with [ extern | commons-logging | [1.0.4,) ] (needed by [[
extern | hibernate | 3.2.1 ]])

It looks like the strict ConflictManager does not support the range
support 1.1 != [1.0.4,)  One package is requesting 1.1, the other is
asking for 1.0.4 or greater. Seems like the both should be happy with
1.1. Is this possible? Thanks

Re: Is this a bug with strict conflict manager? Or does it not support ranges?

[Xavier Hanin <xa...@gmail.com>]

On 4/9/07, Robert Macaulay <ro...@gmail.com> wrote:
>
> If I use
> defaultConflictManager="strict"
>
> I get this
> [ extern | commons-logging | 1.1 ] (needed by [[ extern |
> spring-framework | 2.0.2 ], [ ubs | laredo | working@whou0128628 ]])
> conflicts with [ extern | commons-logging | [1.0.4,) ] (needed by [[
> extern | hibernate | 3.2.1 ]])
>
> It looks like the strict ConflictManager does not support the range
> support 1.1 != [1.0.4,)  One package is requesting 1.1, the other is
> asking for 1.0.4 or greater. Seems like the both should be happy with
> 1.1. Is this possible? Thanks


You're right, strict conflict manager seems to not support dynamic revisions
like version ranges, you can open a JIRA issue for that.

- Xavier




-- 
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/