[Jersey] jersey-spring and maven dependency issues

From: Mohan KR \(mkannapa\) <"Mohan>
Date: Mon, 4 Apr 2011 10:36:05 -0500


  I am trying to integrate jersey-spring, we are in spring 2.5.x stream
currently. I think the module

  is correct, but the "transitive dependencies" is messed up, because of
version ranges (I wish maven

  abandon the version ranges :)). The problem I see is, Spring has decided
to follow their own versioning

  scheme which is *not* compatible with Maven versioning and resolution
algorithm. For e.g 3.0.0.RC2

  will compare as "string" and I think the algorithm reverts to string
compare when resolving a version

  (but in essence things are messed up). Note: IDE's with Maven plugins or
Netbeans (depending on the

  version of embedded Maven) will show completely different resolution of
the transitive dependencies.


  The problem, the spring jersey module activates a default profile
(spring25), and the version for all

  spring dependencies are specified as:




  Now, my issue is this resolves (as of today) to Spring 3.0.0.RC3 (see
previous explanation in first paragraph).

  Now, I have no choice but to use an exclusion element in this dependency
(jersey-spring). My proposal is to

  "lock down" the version (soft) instead of a range, this will ensure at
least 2.5.x is picked up. If min. is 2.5.2,

   can this be changed to:









Mohan KR