james-site-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [James Wiki] Update of "Development/Modularisation" by RobertBurrellDonkin
Date Sun, 11 Feb 2007 10:29:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "James Wiki" for change notification.

The following page has been changed by RobertBurrellDonkin:
http://wiki.apache.org/james/Development/Modularisation

The comment on the change is:
Created space for community to start planning code moves

------------------------------------------------------------------------------
  
  = Execution =
  
- == Stage One ==
+ == Stage One - Prerequisites And Preparation ==
  
+ Before code can be moved out from the pheonix deployment, some prerequisites need to be
completed. This will allow the code moves to be planned whilst these are executed. Space needs
to be created in the subversion tree by pushing the existing code base down a level. A lightweight
ant build framework will be needed to allow efficient creation of modules.
  
  === [COMPLETE] Phase 1 ===
  
@@ -71, +72 @@

   * base builds copies artifacts into stage subdirectory
   * pheonix build copies artifacts locally from stage
   * create macros to allow easy generation of new modules
+ 
+ = Stage Two - Factoring Code Into Modules =
+ 
+ TBD :-)
+ 
+ Recommendations:
+  * Try to avoid splitting packages between modules (good design and also plays well with
modern packaging systems)
+   * This may mean that some repackaging is needed. Recommend that this is done in existing
code (pheonix) before moving the code out into a module (easier to track code changes).
+  * Pheonix coupling should be factored out in the existing code (pheonix) before moving
code out into a module (easier to track code changes) 
+ 
  
  ----
  

Mime
View raw message