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
spring.patch
Description: Binary data
