[James Wiki] Update of "EclipseNotes" by RobertBurrellDonkin

[Apache Wiki <wi...@apache.org>]

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/EclipseNotes

The comment on the change is:
Updated information about eclipse checkout

------------------------------------------------------------------------------
  
  == Check Out James from the Apache SVN repository ==
   *  In the SVN perspective expand the Apache SVN hierarchy to show server/trunk. 
-    *  Right-click on 'trunk', and select 'Checkout' from the pop-up menu.
+    *  Right-click on 'server/trunk', and select 'Checkout' from the pop-up menu.
     *  A dialog window will be present where button 'Finish' can be clicked (assuming that a new project is satisfactory).
     *  From the "New Project Wizard", select Java as the project type and click the "Next" button. 
     *  Specify a project name and location and click the "Next" button. 
@@ -37, +37 @@

  Before attempting to configure Eclipse, verify that you have everything you need by running a build of James outside of Eclipse. This will fetch, or prompt you to fetch, any missing components.
  
   *  Open a shell and switch to the directory into which James was checked out. 
-  *  Run the 'build' script without arguments. 
+  *  Run the Ant 'build' script without arguments. 
   *  When this completes cleanly, the checkout is verified.
  
+ == Modularisation ==
+ 
+ JAMES trunk is a series of modules (See [:Modularisation]). Each module should be a separate project in Eclipse. It is usually convenient to use a separate workspace for JAMES.  
+ 
+ Start by creating a new user library containing all the jars in stage except those starting james-server-*. All projects will need to add this library. The modules use the conventional Maven 2 layout so it's best to set up the defaults for source to src/main/java -> target/classes and src/test/java -> target/test-classes.
+ 
+ For example module, a project needs to be created in Eclipse. This is a slighty labourous process. 
- == Customize Project Settings ==
-  *  Open the Java perspective and select the project.
-  *  From the pop-up menu, select "Properties".
-    *  Select "Java Build Path"
-      *  Select the "Source" tab.
-      * * Select "Use source folders contained in the project".
-      * * Click "Add Existing Folders" and select folder "src/java". 
-      * * Click "OK" and accept the build output folder of "bin".
-      *  Select the "Libraries" tab.
-      * * Ensure exactly one "rt.jar" file is listed and that it is for Java 1.3.1. See the Eclipse help for how to import and specify JVMs with Eclipse.
-      * * Click "Add Jars..." and add every .jar in the James project's "lib" and "phoenix-bin" directories and subdirectories.
-      *  Click "OK" and Eclipse should recompile James without errors.
- You are now ready to develop James in Eclipse.
  
  == Build, Test and Debug Code ==
  As James is a server application I prefer to transfer my updated files to a remote machine, run James' Ant build script (build.bat or build.sh) on the remote machine to update the distribution and then use the Eclipse remote debugger to test. This means that the build, deployment and execution are being tested as they will be used and any changes validated.