For better or worse, if we have the overlay pom inherit the
dependencyManagement from the parent CAS server POM, then everything is
A-okay:
<parent>
<groupId>org.jasig.cas</groupId>
<artifactId>cas-server</artifactId>
<version>3.4-RC2-SNAPSHOT</version>
</parent>
I'm guessing we didn't have this previously because for the longest time the
Spring Web Flow module and us were pretty much in sync. The alternative
would be to exclude spring-webflow and spring-binding when referencing the
ldap support (haven't actually tried this).
On Sat, Feb 27, 2010 at 4:44 PM, Marvin Addison <[email protected]>wrote:
> I've attached the test war overlay project I'm using so we can have a
> common reference for testing solutions going forward.
>
> 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
>
--
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
