Mailet Road Map
The Mailet API and mailet implementations are currently distributed with JAMES server. The API and many matchers and mailets are independent of the JAMES server code. Releasing the API and implementations independently of JAMES server will ease reuse in other containers. It is also hoped that mailet development will be more accessible once factored out from the server.
So, code has been extracted from the JAMES server into a number of mailet related products grouped under http://svn.apache.org/repos/asf/james/mailet/.
The major libraries are as follows:
- mailet-api is the API specification
- mailet-base is a basic mailet development toolkit containing implementation classes closely related to the API
- mailet-standard contains general purpose mailets and matchers with minimal dependencies
In addition, there will be a number of micro-libraries: small, tightly focussed codebases with a single specific aim. Micro-libraries are justifiably popular: they are easy to learn, quick to build, allow dependencies to be tightly controlled and allow more flexible release cycles. For example, crypt-mailets contains a small number of mailets and matchers which perform cryptography using bouncycastle.
Each proposal for a new micro-libraries will be discussed on it's merits.
- move implementation code in the org.apache.mailet namespace from api into base
- decouple mailets and extracting the code from JAMES server
- construct top level mailet website
discuss packaging strategy
discuss release numbering strategy
- release mailet-api
- release mailet-base
- release libraries
- merge improvements
- complete OpenPGP
- release mailet-standard
- release other micro-libraries
JAMES unstable already uses SNAPSHOTs of the new mailet products. It is hoped that future 2.x releases will switch to use these artifacts in due course.