commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (CHAIN-55) split the huge project in submodules
Date Wed, 29 Feb 2012 16:25:57 GMT


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:
>             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|], 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:!default.jspa
For more information on JIRA, see:


View raw message