Hi Ganesh,
CAS war file will run fine by just the default cas overlay pom.xml
(https://github.com/apereo/cas-overlay-template/blob/5.3/pom.xml)
So what to keep really depends on what you need to add beyond the barebone
CAS configuration.
I think for all of the one starting with "cas-server", like:
- cas-server-webapp${app.server},
- cas-server-support-ldap,
- cas-server-support-jdbc,
- cas-server-support-pac4j-webflow,
- cas-server-support-saml,
- cas-server-support-pm,
- cas-server-support-pm-ldap,
- cas-server-support-cookie,
- cas-server-support-throttle
You are intentionally adding them to enable some features, so those
definitely cannot be removed (unless you did not need them anymore)
For the other, you can test whether or not you need the dependency by
simply removing them and see what happens.
If there is any build error or missing features, just add them back in.
Repeat that for all your dependencies and you should be good to go.
I don't think there will be many high risk with the above "try and error"
method as long as your CAS still functional, however of course remove them
at your own risk.
Cheers!
- Andy
--
- 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/5c437751-39ee-4248-94af-38044c7ac439%40apereo.org.
