Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 29 Feb 2012 16:25:57 +0000 (UTC)
From: "Simone Tripodi (Resolved) (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <2130206484.3501.1330532757288.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2063365945.13195.1315004649806.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CHAIN-55) split the huge project in submodules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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