Re: [xwiki-dev] Moving obsolete exo WAR build to sandbox

-1 I don't really see what's broken with exo war. It still seems to build for me using ant. Now there could be some incompatiblities issues because of our changes. Anyway we do want a JSR 168 build and we need to change some config params names to switch from exo to jsr168. Now the same param activates the eXo security. Unfortunately most portals integrations will require authentication integration and the jsr168 spec does not include that integration. Therefore there could still be an exo war with some specific classes for authentication and groups and some modified configuration. So what I would vote for is: - an xwiki-jsr168 module - an xwiki-exo module - an xwiki-jsr168 war artifact with no authentication changes but with jsr168 mode activated in the config - an xwiki-exo war artifact with xwiki-exo module and exo authentication config The xwiki-jsr168 module should allow xwiki to work as is in any jsr168 compatible portal as a drop-in without user integration. Ludovic Vincent Massol a écrit : -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic