On 3/10/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I agree on mime4j, server, jsieve, postage, jspf needing a ttb structure as they follow totally separate workflows, they use different build mechanisms and they are standalone libraries/products.
+1
I think Robert proposed to change only the server folder to split its content into multiple subprojects.
+1 one server sub-project with one version but the code split up into modular sub-components
The current move from trunk to trunk/phoenix-deployment (if I understood him correctly) is only a temporary move: in the end we'll have something similar to: jspf/trunk mime4j/trunk server/trunk/build.xml (to build server and all its modules) server/trunk/phoenix-deployment server/trunk/pop3server server/trunk/smtpserver server/trunk/mailrepository server/trunk/fetchmail server/trunk/spoolmanager This is only a subset of a possible final solution. In the old threads you can find a list of modules we discussed about. Robert probably made a copy&paste to wiki: http://wiki.apache.org/james/Development/Modularisation#head-6070ae830fffd3aa5273d9b50262e904a72f2721
yep just trying to record ideas discussed on list - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
