I made some changes to the cas-server-core and explicitly listed spring-tx and spring-context as a dependency. That seems to ensure that everything uses the right version (without us having to do exclusions). I tried this against RC2-SNAPSHOT (built from trunk)
I was able to get it to work without resorting to a parent for the overlay pom or importing the parent pom. On Sat, Mar 13, 2010 at 7:30 PM, Patrick Berry <[email protected]> wrote: > Gotcha. Good to know. This will at least let me finish testing that > Inspektr issue I was having :) > > On Sat, Mar 13, 2010 at 4:15 PM, Scott Battaglia < > [email protected]> wrote: > >> I'd rather not add these types of exclusions which dependencyManagement is >> supposed to take care of. The reason being that if we miss one, or one of >> our dependencies adds its without us knowing, its going to slip in. We're >> heading down a slippery slope ;-) >> >> I want to look into whether the "import" scope can help us if we tell >> deployers to import the parent pom with scope of "import". I probably won't >> get to try it until later. >> >> Cheers, >> Scott >> >> >> On Sat, Mar 13, 2010 at 7:06 PM, Patrick Berry <[email protected]> wrote: >> >>> >>> >>> On Sat, Mar 13, 2010 at 11:48 AM, Marvin Addison < >>> [email protected]> wrote: >>> >>>> > As I was running out the door to catch my flight, Marvin mentioned >>>> that >>>> > through the power of collaborative ideation the issue had been >>>> resolved. >>>> >>>> I painstakingly added dependency exclusions to get all vestiges of >>>> Spring 2.5.6 out of the resulting overlay, so we have a fix that >>>> doesn't require modifying your overlay. Only problem is that Scott >>>> pointed out maintaining these exclusions over time could be >>>> problematic unless we have a test that will catch them going forward. >>>> I totally agree with that point. We're investigating some POM tweaks >>>> that I'm hopeful may fix the problem without the exclusions. We'll >>>> keep this thread posted as we make progress. >>>> >>>> M >>>> >>>> >>>> >>> >>> I *think* there were two more places that were causing trouble (for me >>> at least). It's taken me a while to soak in this maven dependency thing and >>> figure out what you and Scott were talking about. I've attached a patch >>> that covers the changes I made in cas-server-core/pom.xml >>> and cas-server-support-ldap/pom.xml. Hope I'm doing it right, sorry if the >>> spacing is all screwed up. >>> >>> Pat >>> >>> >>> -- >>> You are currently subscribed to [email protected] as: >>> [email protected] >>> >>> >>> >>> >>> >>> To unsubscribe, change settings or access archives, see >>> http://www.ja-sig.org/wiki/display/JSG/cas-dev >>> >>> >> -- >> You are currently subscribed to [email protected] as: [email protected] >> >> >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev >> >> > -- > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
