Spring dependency causes conflict with older Spring installations...

[Tim Bessie]

Hi all...

I saw someone mentioned some time ago about the issue with
spymemcached requiring Spring 3 to compile, if not to run.

The problem is, when we compile our project (which uses and explicitly
includes) Spring 1.2.6 (yes, rather old), the build drags in both
1.2.6 (for us) and 3.0.3 for you, which causes a conflict at app
startup time (the app will not start).

Isn't there any way you can split off the Spring requirement, since
it's only used in 1 class? It would be nice to be able to use
spymemcached without the expectation that the app was going to be
running a specific Spring version.

Is there a way to mark that the Spring libs should NOT be retrieved
when the WAR is created? If so, this should be in the Wiki somewhere,
I'd think.

- Tim

[Eran Harel]

I know how to do this in Maven, but not in apache-buildr which is what
was used to build spymemcached last time I checked.

On your side, if you're using maven, you can mark the unwanted spring
dependency as "provided".