You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Simone Tripodi (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/29 17:25:57 UTC
[jira] [Resolved] (CHAIN-55) split the huge project in submodules
[ https://issues.apache.org/jira/browse/CHAIN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simone Tripodi resolved CHAIN-55.
---------------------------------
Resolution: Fixed
fixed on r1295177 on trunk
at the end I applied the Niall's suggestion of having 3 modules:
* core
* configuration
* web
without overengineering the modularization in the web package
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira