You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by da...@apache.org on 2002/01/09 22:50:21 UTC

cvs commit: jakarta-james/src/xdocs index.xml install.xml

danny       02/01/09 13:50:20

  Modified:    src/xdocs index.xml install.xml
  Log:
  made a couple of changes to reflect the True Nature of Things
  
  Revision  Changes    Path
  1.9       +12 -14    jakarta-james/src/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/index.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- index.xml	3 Jan 2002 16:46:56 -0000	1.8
  +++ index.xml	9 Jan 2002 21:50:20 -0000	1.9
  @@ -11,22 +11,20 @@
   
   <section name="What is it?">
   
  -  <p>
  -  The Java Apache Mail Enterprise Server (a.k.a. Apache James) is a 100% pure
  -  Java server, designed to be a complete and portable enterprise mail engine solution
  -  based on currently available open protocols (SMTP, POP3, NTTP).  It requires
  -  Java 2 (minimum requirement is the JRE 1.3).
  -  </p>
  +  
  +<p> The Java Apache Mail Enterprise Server (a.k.a. Apache James) is a 100% pure 
  +  Java server, designed to be a complete and portable enterprise mail engine solution 
  +  based on currently available open protocols (SMTP, POP3, NTTP). It requires 
  +  Java 2 (specific requirement is the JRE 1.3, JRE 1.4 is not yet fully supported). 
  +</p>
     <p>Version 2.0a2 is available.  Significant changes have gone into this new release, and we appreciate everyone's contribution! Please let us know what you think.
     </p>
  -  <p><a href="http://jakarta.apache.org/builds/jakarta-james/release/">Binary release of 2.0a2</a>
  -  </p>
  -</section>
  -
  -<section name="Design Objectives">
  -
  -  <p>These are some of the currently implemented features:</p>
  -  <p><i><b>Complete portability</b></i>  Apache James is be a 100% pure Java application
  +  
  +<p><a href="http://jakarta.apache.org/builds/jakarta-james/release/">Binary &amp; 
  +  Source releases of 2.0a2</a> </p>
  +<p>These are some of the currently implemented features:</p>
  +</section><section name="Design Objectives">
  +<p><i><b>Complete portability</b></i>  Apache James is be a 100% pure Java application
          based on the Java 2 platform and the JavaMail 1.2 API.
     </p>
     <p><i><b>Protocol abstraction</b></i>  Unlike other mail engines, protocols are seen only
  
  
  
  1.4       +40 -52    jakarta-james/src/xdocs/install.xml
  
  Index: install.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/install.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- install.xml	3 Jan 2002 16:33:59 -0000	1.3
  +++ install.xml	9 Jan 2002 21:50:20 -0000	1.4
  @@ -4,46 +4,32 @@
   
    <properties>
     <title>Installation</title>
  -  <author email="sergek@lokitech.com">Serge Knystautas</author>
  - </properties>
  -
  -<body>
  -
  -<section name="Step 0: Building. (only necessary for daily snapshots)">
  -
  -  <p>
  -    If you have downloaded a regular distribution, you do not need to
  -    build James.  Proceed directory to Step 1.
  -  </p>
  -
  -  <p>
  -    To compile James from sources you will need <a href="http://jakarta.apache.org/ant/">Ant</a>.
  -    This is a Java-tailored, XML-configured, extensible build or make system.
  -    We are currently using Ant 1.4.
  -  </p>
  -
  -  <p>
  -    If you have downloaded a daily snapshot, you need to build a
  -    distribution.  James includes Ant to compile and package its distribution.
  -    Extract the snapshot to your favorite folder, cd to that folder
  -    and run the "dist" task by calling "build dist".  This will create the
  -    distribution in the "./dist" folder as well as create .tgz and .zip
  -    copies of this folder.  This "./dist" folder is the distribution
  -    folder used in Step 1 and beyond.  You may either cd to ./dist, or
  -    you may copy and rename the dist folder to your new favorite folder.
  -  </p>
  -
  -  <p>
  -  	<strong>Warning!</strong>  Any changes you've made in the 'dist' folder will be lost
  -  	after a recompilation.  If you are making changes to the config.xml or other files, we
  -  	recommend you change the copies in src to avoid losing work.
  -  </p>
  -</section>
  -
  -<section name="Step 1: Installation.">
  -  <p>
  -    Download distibution. Extract all files in your favorite folder.
  -  </p>
  +<author email="sergek@lokitech.com">Serge Knystautas</author> </properties> <body> 
  +<section name="Step 0: Building. (only necessary for daily snapshots)"> 
  +<p> If you have downloaded a binary distribution, you do not need to build James. 
  +  Proceed directory to Step 1. </p>
  +<p> To compile James from sources you need <a href="http://jakarta.apache.org/ant/">Ant</a>. 
  +  This is a Java-tailored, XML-configured, extensible build or make system. We 
  +  are currently using Ant 1.4, which is included in the source distribution.</p>
  +<p> If you have downloaded a daily snapshot, you need to build a distribution. 
  +  James includes Ant to compile and package its distribution. Extract the snapshot 
  +  to your favorite directory, cd to that directory and run the build by calling &quot;build&quot; 
  +  or &quot;./build.sh&quot; which will create an unpacked binary distribution 
  +  in the dist directory, but no archives.</p>
  +<p>This "./dist" directory is the distribution directory used in Step 1 and beyond. 
  +  You may either cd to ./dist, or you may copy and rename the dist directory to your 
  +  installation directory.</p>
  +<p>If you prefer you can run build with the &quot;dist&quot; task "build dist" 
  +  (or &quot;./build.sh dist&quot;). This will create the distribution in the "./dist" 
  +  directory as well as create .tgz and .zip copies of this directory, however it may 
  +  require other resources to build the documentation. </p>
  +<p> <strong>Warning!</strong> Any changes you've made in the 'dist' directory 
  +  will be lost after a recompilation. If you are making changes to the config.xml 
  +  or other files, we recommend you backup and then change the copies in src to 
  +  avoid losing work. </p>
  +</section> <section name="Step 1: Installation."> 
  +<p> Download distibution. Extract or copy all the files in the archive or dist 
  +  directory intto your installation directory. </p>
   </section>
   
   <section name="Step 2: Configuration.">
  @@ -54,11 +40,12 @@
     <p>
       <b>Summary</b> (for impatient people)
     </p>
  -  <p>
  -    M$ users should just run /bin/run.bat. Unix users will find run.sh
  -    under the same folder. A JVM must be in the path.
  -    Running [run* --help] will provide a simple command line help.
  -  </p>
  +  
  +<p> M$ users should just run /bin/run.bat. Unix users will find run.sh under the 
  +  same directory. A JVM must be present and its location specified in the JAVA_HOME 
  +  environment variable. Set this on windows at the command prompt with something 
  +  similar to &quot;set JAVA_HOME=\jdk1.3\bin&quot; on *nix with JAVA_HOME=/jdk1.3/</p>
  +<p> Running [run* --help] will provide a simple command line help. </p>
     <p>
       Most UNIX systems require superuser privileges to open sockets below 1024,
       which includes the IANA-standard SMTP (on port 25) and POP3 (on port 110).
  @@ -66,13 +53,14 @@
       would then need to reconfigure your clients. This may not be an option if
       you want to receive mail from external mailservers.)
     </p>
  -  <p>
  -    The Avalon framework will unpack the neccessay configuration files and wait
  -    for you to configure them. For basic use, you only need to set two items
  -    in the JAMES.conf.xml file: a root password for the remote administration
  -    facility and the IP address of a DNS server. Once you have edited the
  -    configuration files, press 'Enter' on the terminal where Avalon is waiting.
  -  </p>
  +  
  +<p> The Avalon framework will unpack the neccessay configuration files you will 
  +  need to start the server, wait until it is running stop it again (ctrl-c) and 
  +  edit the configuration (thereafter *nix users can run the server in the background 
  +  using ./run.sh &amp;). For basic use, you only need to set two items in the 
  +  JAMES.conf.xml file: a root password for the remote administration facility 
  +  and the IP address of a DNS server. Once you have edited the configuration files, 
  +  press 'Enter' on the terminal where Avalon is waiting. </p>
   </section>
   
   <section name="Step 4: Kickstart.">
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>