> 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

-- 
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

Reply via email to