By: Ian Boston

Ian Boston — Sun, 05 Oct 2008 21:25:18 +0000

Ok so I will be a bit more precise about what A,B,C,D are.

A is a bundle that depends on Spring 2.0.6, and that was specified with ;version=2.0.6
B is a bundle containing Spring 2.0.6
C is SpringDM 1.1.1 which depends on Spring >= 2.5
D is Spring Beans version 2.5.5.A

When A starts is I get log messages of the form
14 == A
3 == D
13 == B

C started Ok.

DEBUG: Constraint violation for 14.0 detected; module can see org.springframework.beans from [3.0] and org.springframework.beans from [13.0]
DEBUG: Constraint violation for 14.0 detected; module can see org.springframework.beans from [3.0] and org.springframework.beans from [13.0]
DEBUG: Constraint violation for 14.0 detected; module can see org.springframework.beans from [3.0] and org.springframework.beans from [13.0]
DEBUG: Constraint violation for 14.0 detected; module can see javax.transaction.xa from [13.0] and javax.transaction.xa from [0]
DEBUG: Constraint violation for 14.0 detected; module can see javax.transaction.xa from [13.0] and javax.transaction.xa from [0]
DEBUG: Constraint violation for 14.0 detected; module can see javax.transaction.xa from [13.0] and javax.transaction.xa from [0]
DEBUG: Constraint violation for 14.0 detected; module can see javax.transaction.xa from [13.0] and javax.transaction.xa from [0]
DEBUG: Constraint violation for 14.0 detected; module can see org.springframework.beans.factory.xml from [3.0] and org.springframework.beans.factory.xml from [13.0]
DEBUG: Constraint violation for 14.0 detected; module can see org.springframework.beans.factory.xml from [3.0] and org.springframework.beans.factory.xml from [13.0]
DEBUG: Constraint violation for 14.0 detected; module can see org.springframework.beans.factory.xml from [3.0] and org.springframework.beans.factory.xml from [13.0]
DEBUG: Constraint violation for 14.0 detected; module can see org.springframework.beans.factory.xml from [3.0] and org.springframework.beans.factory.xml from [13.0]

its quite possible with all the SpringDM extenders and everything else there is something wierd gong on, I will mention it on the Felix lists.

I have found that the autostart load order is relevant.

If I start all of the SPring 2.0.6 and dependencies first, then no problem, but if I start SpringDM and Spring 2.5.5.A first, I get the problems.

By: Stuart

Stuart — Sun, 05 Oct 2008 17:01:56 +0000

Sounds like something else is going on – just because there are >2 versions of a package available shouldn’t stop Bundle A from resolving. Have you mentioned this on the Felix mailing list?

FYI, some people use the following version style:

“[x.y.z, x+1)” ie. “[1.3.0,2)”

where x signifies an incompatible API change. ie: the minimum should be what you test against, and the maximum should be where the next incompatible API change will be.

By: Richard S. Hall

Richard S. Hall — Sun, 05 Oct 2008 15:01:28 +0000

There must be more going on here than you describe, I think. Since there should be no constraint violation unless there is some sort of dependency between bundles A and C. Ultimately, you have to give more details to know what is going on. If you installed all four bundles, B would likely never get used in the first place, since the highest version of the package would get chosen in D.

Post a message on the users@felix mailing list with more details and I am sure there is a reasonable explanation.

Comments on: OSGi version resolution

By: Ian Boston

By: Stuart

By: Richard S. Hall