I agree with Peter; we upgraded from 5.1.3 to 5.3.8 (just finished yesterday), and it wasn't straightforward at all.
I recommend turning on logging for the classes you have changed. Using the debugger might be of use, but for me, trying to trace in Spring applications wasn't useful. YMMV. The granularity of functionality in the web flows had decreased considerably, and the existing web flow for Jetty doesn't work for us. Property names have changed, so that tripped me up for a bit as well. Class packages have changed as well, so if you have overridden classes in the org.apereo.* packages, you may need to hunt about for the new location. Kind regards, Drew -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CACrophb84-ScWxGcGmheVcVhL6Yaf6gjT0%3DiRX-oBda9f%3DCbNQ%40mail.gmail.com.