Hi all
We're trying to set up a set of maven projects which can be used with both
spring 2.5.x and spring 3.0.x. Mostly our applications are currently using
2.5.6 atm, but we'd like to gradually move them over to 3.0.x as time goes on.
Rather than have our libraries and apps hard-code the
Profiles.xml is deprecated and IIRC not supported in M3.
D'oh. If there were a way to do it inside the pom that would definitely be
better (it really isn't an external setting) but I don't see any way to do
that...
Any suggestions gratefully accepted!
Active the profile directly in the
You're going about this the wrong way, IMO. Your Maven
projects should declare its dependencies with GAVs. So if you
have a project (e.g. projectA) using Spring 2.5, that should
be declared in that Maven project. However, if you have some
other project (projectB) depending on projectA, it
The best solution is to have either:
1. A project for spring 3 and a project for spring 2.5 that
defines the dependencyManagement for each of the spring
versions and then use dependency scope import to pull in the
spring 3 or the spring 2.5 dependency version info (assumes
that the
of depMgmt. Very
useful when you work with app servers of different versions
to make it possible to work and test against the exact same
version of dependencies that you will be using in runtime.
/Anders
On Thu, Jun 24, 2010 at 10:26, Dunstan, Tom (SACE Board)
t...@saceboard.sa.gov.au wrote
