[
https://issues.apache.org/jira/browse/JAMES-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit updated JAMES-2394:
----------------------------------
Description:
I would like to propose to re-organize `configure` section of James website.
Currently, many pages about many different topics are mixed together, making it
hard to differenciate the various topics.
Also the current navigation menu do not reflect well the impact of wiring on
the configuration: some components are only available under some packagings,
and thus their configuration is wiring solution specific.
I'd like to subdivide this section into:
{code:java}
- Core components:
- Domain list
- DNS
- Mailet containet
- MailRepositoryStore
- RRT
- Protocols
- SMTP/LMTP
- IMAP4
- POP3
- FetchMail
- Sieve
- Backend specific configuration
- ElasticSearch
- Cassandra
- JPA postgrey
- Spring specific configuration
- mailbox
- events
- quota
- Guice specific configuration
- listeners
- How to...
- Anti-Spam
{code}
We are also missing config about... Tika, WebAdmin, JMAP, JMX, indexer... This
new organisation will allow adding them in the corresponding sections.
was:
I would like to propose to re-organize `configure` section of James website.
Currently, many pages about many different topics are mixed together, making it
hard to differenciate the various topics.
Also the current navigation menu do not reflect well the impact of wiring on
the configuration: some components are only available under some packagings,
and thus their configuration is wiring solution specific.
I'd like to subdivide this section into:
- Core components:
- Domain list
- DNS
- Mailet containet
- MailRepositoryStore
- RRT
- Protocols
- SMTP/LMTP
- IMAP4
- POP3
- FetchMail
- Sieve
- Backend specific configuration
- ElasticSearch
- Cassandra
- JPA postgrey
- Spring specific configuration
- mailbox
- events
- quota
- Guice specific configuration
- listeners
- How to...
- Anti-Spam
We are also missing config about... Tika, WebAdmin, JMAP, JMX, indexer... This
new organisation will allow adding them in the corresponding sections.
> Re-organize configure section
> -----------------------------
>
> Key: JAMES-2394
> URL: https://issues.apache.org/jira/browse/JAMES-2394
> Project: James Server
> Issue Type: New Feature
> Components: configuration, Documentation
> Reporter: Tellier Benoit
> Priority: Major
>
> I would like to propose to re-organize `configure` section of James website.
> Currently, many pages about many different topics are mixed together, making
> it hard to differenciate the various topics.
> Also the current navigation menu do not reflect well the impact of wiring on
> the configuration: some components are only available under some packagings,
> and thus their configuration is wiring solution specific.
> I'd like to subdivide this section into:
> {code:java}
> - Core components:
> - Domain list
> - DNS
> - Mailet containet
> - MailRepositoryStore
> - RRT
> - Protocols
> - SMTP/LMTP
> - IMAP4
> - POP3
> - FetchMail
> - Sieve
> - Backend specific configuration
> - ElasticSearch
> - Cassandra
> - JPA postgrey
> - Spring specific configuration
> - mailbox
> - events
> - quota
> - Guice specific configuration
> - listeners
> - How to...
> - Anti-Spam
> {code}
> We are also missing config about... Tika, WebAdmin, JMAP, JMX, indexer...
> This new organisation will allow adding them in the corresponding sections.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
