> Between 3.5.0 and 3.5.1-SNAPSHOT versions, the size of the webapp has > increased strongly : 22M -> 31M.
That's a ~50% increase. Bummer. > I see that all big libraries come from SAML dependency. > It happens with "CAS-951 Upgrade to OpenSAML 2.x" > https://github.com/Jasig/cas/pull/91/files. > Can we do something for that? Exclude some useless libraries for example > (bouncycastle ?)... The OpenSAML 2.x libs are indeed complex and have a large dependency graph, and I suppose we could develop sufficient tests to determine required dependencies for the narrow uses of SAML support in CAS. But there's always the risk that we might miss something; there's too much surface area to cover in my mind. The value of this effort seems comparatively small. The artifact is ~50% larger, but is a ~30M deployable an obstacle these days? 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
