We have decoupled most of the services from keel-server into their individual modules. Why not go all the way and just move all of them into their own modules? The pro of this is that keel-server becomes the smallest it can be, and the modules are truly treated as "lego blocks". The con is that we get more modules in CVS, and it might be a bit overwhelming to decide what to download.
The remaining services in keel-server are:
org.keel.services.authentication.defaultauth org.keel.services.authorization.defaultauth org.keel.services.cache.excalibur org.keel.services.crypto.base64 org.keel.services.crypto.des org.keel.services.event.defaultauth org.keel.services.filter.filters org.keel.services.model.defaultmodel
I am +1 for moving all "services" out of keel-server. The tie-in comes in the *-deploy.,properties & custom.xml anyway, once that is setup, default-deploy will still work as before. We can update the "default" module in CVS so that you can still download the "required" modules all at once.
Thoughts?
Shash
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
