[ 
https://issues.apache.org/jira/browse/JAMES-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983921#action_12983921
 ] 

Stefano Bagnara commented on JAMES-1184:
----------------------------------------

About utils there is a plan to avoid having it at the api level.

In this plan:
- Green classes can be moved to the only library depending on them 
(Lock+XMLResource to data-library, CombinedInputStream to core)
- Orange classes can be merged to protocol-library (most of them are JMX 
classes and protocol-library is already the home for most jmx stuff). Fetchmail 
will depend on protocols-library then (instead of util).
- Purple classes can be moved to a new library (not sure about the name... 
maybe we can keep util and simply know that libraries do not depends anymore 
from util and we can put util together with libraries in the "layers").
- Yellow classes can be removed, or left together the Purple ones.

This does not reduce the number of modules but reduce the size of the util 
module and bring it at the "library" layer so in the api layer we just have 
real apis.

As per the "multilevel" comment I'm just writing this as loud-thinking... just 
a place to scratchpad some thought as I have no time to do better analysis of 
pro/cons of both changes now


> Modules consolidation
> ---------------------
>
>                 Key: JAMES-1184
>                 URL: https://issues.apache.org/jira/browse/JAMES-1184
>             Project: JAMES Server
>          Issue Type: Task
>          Components: Build System
>    Affects Versions: 3.0-M2
>            Reporter: Stefano Bagnara
>            Assignee: Stefano Bagnara
>             Fix For: 3.0-M3
>
>         Attachments: graph-server-utils.gif, graph-server.gif
>
>
> Just opening it to keep track of the proposal to the mailing list.
> ------------
> - mail-file(3)
> - mail-jcr(1)
> - mail-jdbc(3)
> - user-jpa(4)
> - user-file(2)
> - user-jcr(2)
> - user-jdbc(4)
> - domainlist-jpa(2)
> - domainlist-xml(1)
> I only see benefits and no drawbacks in consolidating the 9 modules
> above to the following 4 modules:
>  persistence-jpa(6) = user-jpa(4)+domainlist-jpa(2)
>  persistence-file(6) = user-file(2)+mail-file(3)+domainlist-xml(1)
>  persistence-jcr(3) = user-jcr(2)+mail-jcr(1)
>  persistence-jdbc(7) = user-jdbc(4)+mail-jdbc(3)
> - mail-library(1)
> - domainlist-library(2)
> - user-library(9)
> We could consolidate them into a persistence-library module (from 3 to
> 1 module).
>  persistence-library(12) =
> mail-library(1)+domainlist-library(2)+user-library(9)
> - queue-library(2)
> - queue-jms(5)
> We could merge queue-library to queue-jms (a library module makes
> sense when we do something useful.. if it is trivial stuff it can be
> duplicated or moved to the api layer).
>  queue-jms(7) = queue-jms(5)+queue-library(2)
> -------------------------
> It seems there is agreement on the merging. We still have to decide whether 
> to name the modules "persistence-${type}" or simply "${type}" (or maybe 
> "data-${type}")

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to