james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin" <robertburrelldon...@gmail.com>
Subject [VOTE] Mailets -> Mailet subproject
Date Sun, 02 Mar 2008 20:59:51 GMT
though the mailet API has been moved to the mailet subproject, mailet
implementations are still contained in the server codebase. managing
mailets as part of the mailet sub-project will allow releases to be
made independent of the JAMES server, reduce the learning time
required before developers can contribute, improve modularity in the
JAMES core and allow libraries to be shared between different JAMES
versions (allowing bugs to be fixed in one place).

though some mailets are too tightly coupled to be moved immediately,
others  can be moved with no or minimal effort. some extra work will
be required to produce a good website but these practicality can be
resolved once consensus about the principle has been established.

proposal
--------------
establish the ideal that mailets should not depend on JAMES and should
be managed within the mailet subproject rather than the server
project. a home for mailets should be created within the mailet
subproject and mailets gradually moved to it over time.

here's my +1

- robert

-- 8<------------------------------------------------------------------
[ ] +1 Move Mailets to Mailet subproject
[ ] +0 Sounds reasonable
[ ] -0 Sounds unreasonable
[ ] -1 Do not move Mailets to Mailet subproject
-------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message