[ 
https://issues.apache.org/jira/browse/CHAIN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097642#comment-13097642
 ] 

Niall Pemberton commented on CHAIN-55:
--------------------------------------

I agree with splitting the modules, mainly because I think the "web" elements 
are off-putting for users who want a simple CoR pattern. But I would keep the 
"web" components (i.e. Servlet, Portlet, Faces) together as a single module. 
This would allow WebContext & the Get/SetLocaleCommands to be part of the "web" 
module, rather than having to put it  in the "core APIs" (since Servlet, 
Portlet & Faces implement them). Marking portlet & faces dependencies as 
"optional" in the pom.xml would prevent unnecessary dependencies being included.

> split the huge project in submodules
> ------------------------------------
>
>                 Key: CHAIN-55
>                 URL: https://issues.apache.org/jira/browse/CHAIN-55
>             Project: Commons Chain
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Simone Tripodi
>            Assignee: Simone Tripodi
>             Fix For: 2.0
>
>
> As discussed in the [dev ML|http://markmail.org/message/pnyin5xzmxt2up5q], 
> there is a general agreement between people interested on chain, on splitting 
> the huge component in small submodules, in order to have a lightweight, 
> dependencies-less (unless the logging library, if required) and 
> self-contained core module, and users interested on core APIs only don't need 
> to bring unused code in their applications. SUggested modules are:
>  * core APIs;
>  * XML configuration APIs (depends from Digester);
>  * servlet (depends from Servlet APIs);
>  * portlet (depends from Portlet APIs);
>  * faces (depends from Faces APIs).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to