portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tay...@apache.org
Subject cvs commit: jakarta-jetspeed-2/docs/release RELEASE-TODO.txt JETSPEED-2.0-M1-README.txt
Date Sun, 05 Dec 2004 06:38:35 GMT
taylor      2004/12/04 22:38:35

  Modified:    docs/release JETSPEED-2.0-M1-README.txt
  Added:       docs/release RELEASE-TODO.txt
  Log:
  updated README for release -- needs  to be uploaded to distribution directory onportals
  new RELEASE-TODO still under construction
  
  Revision  Changes    Path
  1.2       +34 -0     jakarta-jetspeed-2/docs/release/JETSPEED-2.0-M1-README.txt
  
  Index: JETSPEED-2.0-M1-README.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-jetspeed-2/docs/release/JETSPEED-2.0-M1-README.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- JETSPEED-2.0-M1-README.txt	5 Dec 2004 04:29:10 -0000	1.1
  +++ JETSPEED-2.0-M1-README.txt	5 Dec 2004 06:38:35 -0000	1.2
  @@ -2,6 +2,13 @@
    Jetspeed 2.0-M1 Release
   --------------------------
   
  +Tested App Servers:
  +
  + * Tomcat 4.1.30
  + * Tomcat 5.0.30
  +
  + (Tomcat 5.5 requires a different jetspeed.xml found in the source tree under src/resources/jetspeed-tomcat-5.5.xml)
  +
   
   Installation Instructions
   --------------------------
  @@ -49,4 +56,31 @@
           $TOMCAT_HOME/shared/lib/portlet-api*.jar
           $TOMCAT_HOME/shared/lib/portals-bridges*.jar
           $TOMCAT_HOME/webapps/jetspeed
  +
  +
  +Deployment Optimization
  +-----------------------------
  +There are some known issues with deployment and race conditions with the default jetspeed
configuration.
  +To optimize deployment, add these properties to your $HOME/build.properties:
  +
  +org.apache.jetspeed.services.autodeployment.user = admin
  +org.apache.jetspeed.services.autodeployment.password = admin
  +
  +Edit your $TOMCAT_HOME/conf/tomcat-users.xml and add the required manager and admin roles
and admin user:
  +
  +<?xml version='1.0' encoding='utf-8'?>
  +<tomcat-users>
  +  <role rolename="manager"/>
  +  <role rolename="admin"/>
  +  ...
  +  <user username="admin" password="admin" roles="admin,manager,user"/>
  +</tomcat-users>
  +
  +
  +If you make these changes, its recommended to change Tomcat's server.xml and turn off Autodeployment
feature:
  +
  +      <Host name="localhost" debug="0" appBase="webapps"
  +       unpackWARs="true" autoDeploy="false">  <------------------
  +
  +
   
  
  
  
  1.1                  jakarta-jetspeed-2/docs/release/RELEASE-TODO.txt
  
  Index: RELEASE-TODO.txt
  ===================================================================
  1. update project.xml and etc/project-dependencies/*.xml in all projects to 2.0-Mx
  
  2. delete old versions of jars from shared/lib
  
  3. checkout to a clean directory
  
  4. build with tests on all db platforms (hsql, mysql, oracle...)
  
  5. test running app in Tomcat
  
  6. build with Hypersonic
      maven -o allClean allBuild
      maven -o quickStart
  
  7. From Tomcat dir, make a copy of the binary release in format:
      {tomcat-root}
          |
          | - webapps/jetspeed 
          | - jetspeed.xml
          | - conf/Catalina/localhost/jetspeed.xml
          | -
          | - jetspeed-database
                 |- hsql
                     -| Production
                 |
                 |- scripts
  
              - start-database.sh
              - start-database.bat
              - hsqldb-1.7.1.jar
  
     remove everything else but the files above making an overlay
  
  8. create a windows zip and unix tar.gz of the directory named:
  
      jetspeed-2.0-M1.zip
      jetspeed-2.0-M1.tar.gz
  
  9. create the README for the specific version, see docs/release/JETSPEED-README-2.0-M1.txt
  
  10. tag the release from Eclipse or command line using tag format:
   
        JETSPEED-RELEASE-2-0-M1
  
  11. get a clean checkout, don't build anything
  
  12. create a tar and zip of the entire build directory jakarta-jetspeed-2 named:
  
      jetspeed-2.0-M1-src.tar.gz
      jetspeed-2.0-M1-src.zip
  
  13. Sign the distributions
  
      distribution dir == /www/www.apache.org/dist/portals/jetspeed-2/
  
      a. Download the KEYS from the distribution directory 
      b. Export your public key 
                                          
          gpg --list-sigs <your name> >> KEYS
          gpg --armor --export <your name>) >> KEYS
  
      b. Add the contents of th KEYS to your public ring 
  
          gpg --import KEYS
  
      c. Generate the .asc files using:
  
          gpg -sab jetspeed-2.0-M1.zip
          gpg -sab jetspeed-2.0-M1.tar.gz
          gpg -sab jetspeed-2.0-M1-src.zip
          gpg -sab jetspeed-2.0-M1-src.tar.gz
  
      d. Generate the .md5 hashes:
  
          openssl md5 < jetspeed-2.0-M1.zip > jetspeed-2.0-M1.zip.md5
          openssl md5 < jetspeed-2.0-M1.tar.gz > jetspeed-2.0-M1.tar.gz.md5
          openssl md5 < jetspeed-2.0-M1-src.zip > jetspeed-2.0-M1-src.zip.md5
          openssl md5 < jetspeed-2.0-M1-src.tar.gz > jetspeed-2.0-M1-src.tar.gz.md5
  
      e. upload the files to the distributions directory
  
   14. Create Symbolic Links to Current 
  
   left off here...
  
   xx. Write and post release announcements to mailing lists:
  
      general@portals.apache.org
      jetspeed-dev@jakarta.jetspeed.org
      jetspeed-users@jakarta.jetspeed.org
      announcements@jakarta.apache.org
  
  
  
  
  
  

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


Mime
View raw message