In my project there are many direct and indirect dependencies at the
lowest level on springframework jars.
One such dependency requires use of the most recent springframework
jars. Migrating to latest version of spring is my projects direct
dependency causes
problems at runtime with other
in most recent versions of Maven, dependencyManagement can be used to
enforce a particular version throughout the entire tree.
You can also use the enforcer plugin to ensure this has been properly applied.
Cheers,
Brett
2008/8/26 Farrukh Najmi [EMAIL PROTECTED]:
In my project there are many
appreciate any advice. Thanks.
--
View this message in context:
http://www.nabble.com/How-to-cope-with-conflicting-jar-versions-tp19150279p19153947.html
Sent from the Maven - Users mailing list archive at Nabble.com
versions
of
apis from spring and its dependencies.
Is there a good way to deal with this dependency hell? If so I would
appreciate any advice. Thanks.
--
View this message in context:
http://www.nabble.com/How-to-cope-with-conflicting-jar-versions-tp19150279p19153947.html
Sent from
On Mon, Aug 25, 2008 at 3:40 PM, Farrukh Najmi
[EMAIL PROTECTED] wrote:
In my project there are many direct and indirect dependencies at the lowest
level on springframework jars.
One such dependency requires use of the most recent springframework jars.
Migrating to latest version of spring
thirdly version ranges give you deterministic and manageable conflicts.
however in the case of spring you should not be mixing the different major
revisions that will just give you headaches... use one or the other
1.2.X not compatible with 2.0.X not compatible with 2.5.X, i use version
ranges
