You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Eric Charles (Created) (JIRA)" <se...@james.apache.org> on 2012/01/08 10:10:39 UTC
[jira] [Created] (JAMES-1362) Nest server modules
Nest server modules
-------------------
Key: JAMES-1362
URL: https://issues.apache.org/jira/browse/JAMES-1362
Project: JAMES Server
Issue Type: Improvement
Components: Build System
Affects Versions: Trunk
Reporter: Eric Charles
Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1362) Nest server modules
Posted by "Stefano Bagnara (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183395#comment-13183395 ]
Stefano Bagnara commented on JAMES-1362:
----------------------------------------
Things I noticed working on the dependency graph:
1) queue-api and mailetcontainer-api are used only by functions and not by libraries
2) dnsservice-api, lifecycle-api and filesystem-api are used by more than 1 *library* and by many functions, so they are really at our "core": maybe we should simply merge them.
3) data-api, instead, is used only by 1 library (data-library) and by many functions. "mailets" is the only "non data function" to depend on data-library (and we should try to remove this dependency). data-* seems to be the most vertical issue we have in server because other modules (but mailets) do only depends on data-api and nothing else (I don't see it as a candidate for a standalone product because api are very specific to how james do things, but could be an option if the api is improved and made more generic).
4) "core" does not depend on "util". The only library using util is "protocols-library". Otherwise only "functions" depends on util content: it would be cool to be able to remove the util module at all.
5) lifecycle-spring has only 1 inbound arrow from container-spring: why can't we merge it container-spring?
6) the "api" part of the mailetcontainer-api could be pushed to mailet-api in a container package: they are very simple interfaces (MailProcessor is a subset of Mailet).
7) dnsservice-library depends by dnsservice-api but despite the name it is not used by dnsservice-dnsjava function implementation. Instead it contains some dnsservice-api based utilities (so maybe we can merge it to another library module (every module depending on dnsservice-library also depends on core-library, so core-library sounds like a good destination).
No time now for further considerations (I will just upload a couple of grouping experiments I did in order to keep dependencies "clean").
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
> Attachments: graph-server-modules-nodeps-20120110.gif, graph-server-modules-withdeps-20120110.gif
>
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Issue Comment Edited] (JAMES-1362) Nest server modules
Posted by "Stefano Bagnara (Issue Comment Edited) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183172#comment-13183172 ]
Stefano Bagnara edited comment on JAMES-1362 at 1/10/12 10:00 AM:
------------------------------------------------------------------
Call me "limited"/"rigid" but I am against any grouping with circular/twisted dependencies.
Even ignoring the dependency issue I don't find it "useful", e.g:
- I can't imagine anyone using only the dns group outside james
- mailetcontainer and mailets have nothing to do each other. mailets contains very james specific classes, instead mailetcontainer is a more generic library.
- If we identify functional some group that "makes sense" then we should try to remove dependencies from other groups and move them to separate products (like protocols, mailbox, jspf, etc). So after you extract the "generic library" a group like "queue" would only contain 3-4 adapter classes. So the grouping doesn't correctly react to refactoring.
- Now that we extracted imap/protocols/mailets, james-server (escluding tests) is 2.4MB of java sources, less than 400 files. IMO it is not "so big" to require more organization (so I would embrace grouping only if I see a lot of value in it). You referenced Hadoop in another thread: hadoop has 4 base java modules and each one big as the whole james-server (core, mapred, hdfs, contrib modules are between 2 and 3MB java sources each one).
- I think our api modules are not "well-thought" (I'm guilt for this, too) but instead they are the results of fast dependency analysis and code refactorings (e.g: filesystem api is 1 class, lifecycle 4 class, dns-api 3 classes, queue-api 5 classes, mailetcontainer-api 7 classes). So I expect api modules to change, to see some merge between them and maybe some completely different aggregation on the api layer. This grouping would make a similar refactoring an harder task. At the current state I would prefer to have a single api module (we already have packages to separate concerns and most modules depends on more than half of that api modules).
- IMO James-server needs some more care/organization on the java architecture before we organize *current* java files even more than we already did.
That said I'm not active on the code, so I just wanted to give explanations on my thoughts and now I will better leave the decision to active committers (if I find some time I will try to create an updated dependency graph of the current modules as what I wrote is based on what we had in trunk 1 year ago and I may have missed some major changes).
was (Author: bago):
Call me "limited"/"rigid" but I am against any grouping with circular/twisted dependencies.
Even ignoring the dependency issue I don't find it "useful", e.g:
- I can't imagine anyone using only the dns group outside james
- mailetcontainer and mailets have nothing to do each other. mailets contains very james specific classes, instead mailetcontainer is a more generic library.
- If we identify functional some group that "makes sense" then we should try to remove dependencies from other groups and move them to separate products (like protocols, mailbox, jspf, etc). So after you extract the "generic library" a group like "queue" would only contain 3-4 adapter classes. So the grouping doesn't correctly react to refactoring.
- Now that we extracted imap/protocols/mailets, james-server (escluding tests) is 2.4MB of java sources, less than 400 files. IMO it is not "so big" to require more organization (so I would embrace grouping only if I see a lot of value in it). You referenced Hadoop in another thread: hadoop has 4 base java modules and each one big as the whole james-server (core, mapred, hdfs, contrib modules are between 2 and 3MB java sources each one).
- I think our api modules are not "well-thought" (I'm guilt for this, too) but instead they are the results of fast dependency analysis and code refactorings (e.g: filesystem api is 1 class, lifecycle 4 class, dns-api 3 classes, queue-api 5 classes, mailetcontainer-api 7 classes). So I expect api modules to change, to see some merge between them and maybe some completely different aggregation on the api layer. This grouping would make a similar refactoring an harder task. At the current state I would prefer to have a single api module (we already have packages to separate concerns and most modules depends on more than half of that api modules).
- IMO James-server needs some more care/organization on the java architecture before we organize *current* java files even more than we already did.
That said I'm not active on the code, so I just wanted to give explanations on my thoughts and now I will better leave the decision to active committers (if I find some time I will try to create an updated dependency graph of the current modules as what I wrote is based on what we had in trunk 1 year ago and I may have missed some major changes).
For easier historical navigation I add a link to an older issue:
https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1362) Nest server modules
Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183193#comment-13183193 ]
Eric Charles commented on JAMES-1362:
-------------------------------------
Hi Stefano,
Thx for your replies and valuable ideas.
Are you calling for a server modules refactoring?
About your points, I will try to answer one by one:
- dns: all groups are not obliged to be used ouside james
- mailets: I remember you pushed to have mailets not depend at all on server. For now, it's the case, so any place would be a non-optimal place
- my goal was not to make those groups separate products (we already have enough, think to release,...), but rather to have a better understanding of the functions fullfilled by server in the developer eyes.
- I understand you are calling for refactoring (this could include some grouping or not)
- api: depends if we target one single api for server, or for potential subgroups. If you go for one api for server as pre-requesite, you make the grouping option obsolete.
- I find we are not so fare away from something good on modules (sidenote: maybe we should better release, module split/resplit won't help end users)
- +1 if you can find time to replay your dependency graph and continue the discussion to help find the correct solution.
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1362) Nest server modules
Posted by "Stefano Bagnara (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183172#comment-13183172 ]
Stefano Bagnara commented on JAMES-1362:
----------------------------------------
Call me "limited"/"rigid" but I am against any grouping with circular/twisted dependencies.
Even ignoring the dependency issue I don't find it "useful", e.g:
- I can't imagine anyone using only the dns group outside james
- mailetcontainer and mailets have nothing to do each other. mailets contains very james specific classes, instead mailetcontainer is a more generic library.
- If we identify functional some group that "makes sense" then we should try to remove dependencies from other groups and move them to separate products (like protocols, mailbox, jspf, etc). So after you extract the "generic library" a group like "queue" would only contain 3-4 adapter classes. So the grouping doesn't correctly react to refactoring.
- Now that we extracted imap/protocols/mailets, james-server (escluding tests) is 2.4MB of java sources, less than 400 files. IMO it is not "so big" to require more organization (so I would embrace grouping only if I see a lot of value in it). You referenced Hadoop in another thread: hadoop has 4 base java modules and each one big as the whole james-server (core, mapred, hdfs, contrib modules are between 2 and 3MB java sources each one).
- I think our api modules are not "well-thought" (I'm guilt for this, too) but instead they are the results of fast dependency analysis and code refactorings (e.g: filesystem api is 1 class, lifecycle 4 class, dns-api 3 classes, queue-api 5 classes, mailetcontainer-api 7 classes). So I expect api modules to change, to see some merge between them and maybe some completely different aggregation on the api layer. This grouping would make a similar refactoring an harder task. At the current state I would prefer to have a single api module (we already have packages to separate concerns and most modules depends on more than half of that api modules).
- IMO James-server needs some more care/organization on the java architecture before we organize *current* java files even more than we already did.
That said I'm not active on the code, so I just wanted to give explanations on my thoughts and now I will better leave the decision to active committers (if I find some time I will try to create an updated dependency graph of the current modules as what I wrote is based on what we had in trunk 1 year ago and I may have missed some major changes).
For easier historical navigation I add a link to an older issue:
https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1362) Nest server modules
Posted by "Stefano Bagnara (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183320#comment-13183320 ]
Stefano Bagnara commented on JAMES-1362:
----------------------------------------
- mailets: we already extracted generic mailets to a separate product. If we are able to make other mailets more generic then they will move to the already existing product. So james-mailet module will always be a james specific module not useable outside james.
- api/refactoring: my call is that before moving stuff "again" we should think if we really need 6 micro-api-modules (in the current code I would simply prefer to have a single api module, but the best thing would be to first improve the api and then see how to better organize it in modules).
- +1 to release early :-)
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1362) Nest server modules
Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183327#comment-13183327 ]
Eric Charles commented on JAMES-1362:
-------------------------------------
I will set this on-hold and will put more effort reviewing the needed remaining actions for the release.
Atm, this does not bring real value to the end-user.
I may re-raise it once again later :).
Thx.
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1362) Nest server modules
Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189685#comment-13189685 ]
Eric Charles commented on JAMES-1362:
-------------------------------------
Hi Stefano,
Thx for the diagrams update.
As this is a big change, we must further think about it.
For now, I will not change anything, and simply bring the following renaming which does not impact to the modules structure:
- prefix jcr, jdbc, jpa, ldap with data-: this was discussed during your previous refactoring, and there was no strong committment for an option or the other. Living a while with it, I prefer going to data-...
- prefix imapserver, smtpserver, pop3server to protocols-imap, protocols-smtp, protocols-pop3: since the introduction of protocols-library module in server, this makes more sense.
Thx,
Eric
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
> Attachments: graph-server-modules-groups-20120110.gif, graph-server-modules-groups2-20120110.gif, graph-server-modules-nodeps-20120110.gif, graph-server-modules-withdeps-20120110.gif
>
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Updated] (JAMES-1362) Nest server modules
Posted by "Stefano Bagnara (Updated) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefano Bagnara updated JAMES-1362:
-----------------------------------
Attachment: graph-server-modules-withdeps-20120110.gif
graph-server-modules-nodeps-20120110.gif
Dependencies graphs with and without external dependencies (in both cases external dependencies belonging to a single module have been collapsed in the module... so this show only external "shared" dependencies)
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
> Attachments: graph-server-modules-nodeps-20120110.gif, graph-server-modules-withdeps-20120110.gif
>
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1362) Nest server modules
Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183133#comment-13183133 ]
Eric Charles commented on JAMES-1362:
-------------------------------------
Hi,
I made a new attempt (see groups hereafter).
The idea is to tend to functional groups (for example to have a group that allows the queueing of mails, namely the 'queue' group).
Of course, the queue group can not work without dependencies coming some other groups, but can not work without activemq dependencies either. So I don't see any problem stating this is an independent group, even it depends on other groups.
A module within a group should also depend on api module that reside in other group, ideally not to library or implementation from other group. I prefer having the api in each group, rather than a top api group.
Heads up,
Eric
dns
dnsservice-api
dnsservice-library
dnsservice-dnsjava
protocols
fetchmail
imapserver
lmtpserver
protocols-library
pop3server
smtpserver
data
data-api
data-library
hbase
jpa
jcr
jdbc
ldap
mailet
mailetcontainer-api
mailetcontainer-camel
mailets
queue
queue-api
queue-file
queue-jms
queue-activemq
container
filesystem-api
lifecycle-api
container-spring
lifecycle-spring
file
core
util
cli
mailbox-adapter
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Updated] (JAMES-1362) Nest server modules
Posted by "Stefano Bagnara (Updated) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefano Bagnara updated JAMES-1362:
-----------------------------------
Attachment: graph-server-modules-groups2-20120110.gif
graph-server-modules-groups-20120110.gif
First test tries to mix group by "role" with dependency requirements, second one group strictly by "dependency layer".
> Nest server modules
> -------------------
>
> Key: JAMES-1362
> URL: https://issues.apache.org/jira/browse/JAMES-1362
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Trunk
> Reporter: Eric Charles
> Attachments: graph-server-modules-groups-20120110.gif, graph-server-modules-groups2-20120110.gif, graph-server-modules-nodeps-20120110.gif, graph-server-modules-withdeps-20120110.gif
>
>
> Group server module by function based on proposal found on https://issues.apache.org/jira/browse/JAMES-1184?focusedCommentId=12983893&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12983893
> I will publish here the resulting nesting before committing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org