Greetings, It seems that CAS 3.4.3, perhaps older, is requiring the use of Hibernate. I have a simple WAR overlay POM in my utilities projects and at the top level we've initiated a migration away from Hibernate, and accompanying it with m-enforcer-p bans on dependencies. CAS seems to require Hibernate even when we do not knowingly utilize any sort of Hibernate/JPA persistence options..
Is it possible some Hibernate dependencies are defined up in the chain a little higher than actually required? It would be nice if we didn't have to include dependencies which weren't actually used, and it would also doubly help to get process police off my back. Thanks! -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. -- 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-user
