> I like the idea and I don't want to pretend I already did the work, but I've > moved a lot of classes from core to the server and management webapps when I > extracted the services management from the CAS server.
I was thinking of this point. The existing split-brain state of Web components, some in core, some in webapp, is troublesome. I'm wholeheartedly in favor of putting them exclusively in one module or another. It's a headache for us and likely other deployers having them split fairly arbitrarily between two modules at present. Unless we can make an argument for another kind of webapp that needs Web components that is _not_ an overlay, then I would argue it's safe to complete the migration of classes in the org.jasig.cas.web package (and possibly others) into cas-server-webapp. I'd like to see a complete listing of "Web" components that would be affected by this move. The package I mentioned seems obvious, but it may be more nuanced than that. M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
