[cas-dev] Building CAS 3.3 from HEAD

[dale77]

I was able to revert my POM additions and still get a good build, possibly
moving from maven 2.0.7 to 2.0.9 solved most of my issues.

The change in deployerConfigContext.xml that caused me problems was the move
from org.acegisecurity.userdetails.memory.InMemoryDaoImpl to
org.springframework.security.userdetails.memory.InMemoryDaoImpl. I just
brought our list of valid admins over from 3.2 and didn't notice the class
name change.

Can you have a look at my comments against
http://www.ja-sig.org/issues/browse/CAS-687. There is one small bug with a
message in there.


scott_battaglia wrote:
> 
> There shouldn't have been too many changes between 3.2 and 3.3 in terms of
> the deployerConfigContext.xml IIRC.
> 
> If there's anything we need to change to the CAS POMs let me know.
> -Scott
> 

-- 
View this message in context: http://www.nabble.com/Building-CAS-3.3-from-HEAD-tp18722832p18725628.html
Sent from the CAS Dev mailing list archive at Nabble.com.