Hello Benoit,
This is also the thing I want to do when the first time enters James'
repository. Too many subdirectories in the root.
One concern should put "not primary things" in the separate parent
directory. Ex: benchmark, dockerfile, docs, grafana-reporting,
third-party, testing...
/Regards,/
//
/Tung, Tran Van/
On 07/06/2021 18:21, [email protected] wrote:
Hello people,
On my crusade to reorganize James code related to Guice apps (and
promote their adoption), I come to the next item of the tick list (after
ZIP packaging, JIB packaging to enable distribution).
I would like to make those application easier to find in the source tree.
Here would be the principles I would like to enforce:
- All server applications should be collocated under the same directory
- Server application modules should be clearly separated from guice
module declarations
I do not intend to fully reorder James directories just now but rather
take small steps in a globally consensual direction. As such I propose
the following directory layout as a first step:
```
server/apps/spring
-> today server/app
server/apps/memory
-> today server/container/guice/memory-guice
server/apps/cassandra
-> today server/container/guice/cassandra-guice
server/apps/cassandra-ldap
-> tests only
server/apps/distributed
-> today server/container/guice/cassandra-rabbitmq-guice
server/apps/cassandra-ldap
-> tests only
server/apps/jpa
-> today server/container/guice/jpa-guice
server/apps/jpa-smtp
-> today server/container/guice/jpa-smtp
server/container/guice/*
-> Location of guice modules, lifecycle, etc...
server/container/spring/*
-> Location of Spring stuff...
```
Would we reach a consensus of the usefulness of such a move before I
invest my time on it?
Regards,
Benoit
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
