Return-Path: Delivered-To: apmail-geronimo-scm-archive@www.apache.org Received: (qmail 95322 invoked from network); 7 Oct 2009 15:50:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Oct 2009 15:50:57 -0000 Received: (qmail 8436 invoked by uid 500); 7 Oct 2009 15:50:56 -0000 Delivered-To: apmail-geronimo-scm-archive@geronimo.apache.org Received: (qmail 8366 invoked by uid 500); 7 Oct 2009 15:50:56 -0000 Mailing-List: contact scm-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list scm@geronimo.apache.org Received: (qmail 8297 invoked by uid 99); 7 Oct 2009 15:50:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 15:50:56 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED,URIBL_RED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 15:50:48 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 0599B238888D; Wed, 7 Oct 2009 15:50:27 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r822783 - in /geronimo/server/branches/2.2: BUILDING.txt README.txt RELEASE_NOTES-2.2-SNAPSHOT.txt Date: Wed, 07 Oct 2009 15:50:26 -0000 To: scm@geronimo.apache.org From: dwoods@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20091007155027.0599B238888D@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: dwoods Date: Wed Oct 7 15:50:26 2009 New Revision: 822783 URL: http://svn.apache.org/viewvc?rev=822783&view=rev Log: update building.txt to say maven 2.0.10+, which is what genesis-2.0 enforces. update formating on other txt files to better fit within a 80 char width window. Modified: geronimo/server/branches/2.2/BUILDING.txt geronimo/server/branches/2.2/README.txt geronimo/server/branches/2.2/RELEASE_NOTES-2.2-SNAPSHOT.txt Modified: geronimo/server/branches/2.2/BUILDING.txt URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.2/BUILDING.txt?rev=822783&r1=822782&r2=822783&view=diff ============================================================================== --- geronimo/server/branches/2.2/BUILDING.txt (original) +++ geronimo/server/branches/2.2/BUILDING.txt Wed Oct 7 15:50:26 2009 @@ -21,7 +21,7 @@ To build you will need: * JDK 5.0+ (J2SE 1.5.0+) (http://java.sun.com/j2se/1.5.0) - * Maven 2.0.9+ (http://maven.apache.org) + * Maven 2.0.10+ (http://maven.apache.org) For detailed instructions please see: @@ -67,10 +67,10 @@ mvn site -Denv=site If you attempt to run `mvn clean install site` strange errors are bound to occur -which will drive you crazy and you may start pulling your hairout... so its not +which will drive you crazy and you may start pulling your hair out... so its not recommended. -It is important to specify `-Denv=site` to limit the modules which are processed, -as many of the configs modules will freak-out. +It is important to specify `-Denv=site` to limit the modules which are +processed, as many of the configs modules will freak-out. Modified: geronimo/server/branches/2.2/README.txt URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.2/README.txt?rev=822783&r1=822782&r2=822783&view=diff ============================================================================== --- geronimo/server/branches/2.2/README.txt (original) +++ geronimo/server/branches/2.2/README.txt Wed Oct 7 15:50:26 2009 @@ -17,25 +17,25 @@ Documentation ====================== - This README serves as quick introduction to Geronimo. More complete documentation - can be found here: + This README serves as quick introduction to Geronimo. More complete + documentation can be found here: - http://cwiki.apache.org/GMOxDOC22/documentation.html OR - http://cwiki.apache.org/GMOxDOC21/documentation.html - (Geronimo 2.1 documentation until Geronimo @VERSION@ documentation is created) ______________________ Installing Geronimo ====================== - To install Geronimo, simply unpack the .zip (Windows) or tar.gz (Unix) file containing - Geronimo. + To install Geronimo, simply unpack the .zip (Windows) or tar.gz (Unix) file + containing Geronimo. Note for Windows platforms: The maximum path length for a directory path is 255 characters. Installing - Geronimo into a long directory path may cause the installation or server start up to fail. + Geronimo into a long directory path may cause the installation or server + startup to fail. It is recommended that you use a short directory name, such as "c:\g\". @@ -43,14 +43,13 @@ Starting Geronimo ====================== - There are three general techniques for starting Geronimo (assuming the current directory - is ): + There are three general techniques for starting Geronimo (assuming the current + directory is ): 1. GShell -- "./bin/gsh geronimo/start-server" 2. Script -- "./bin/geronimo.sh run" 3. Java -- "java -Djava.endorsed.dirs=$JRE_HOME/lib/endorsed:lib/endorsed -Djava.ext.dirs=$JRE_HOME/lib/ext:lib/ext -javaagent:bin/jpa.jar -jar bin/server.jar" - Additional information on command environments can be found below. @@ -60,29 +59,31 @@ Applications can be deployed to a Geronimo server in several ways: - 1. Administrative command scripts -- "./bin/gsh deploy/deploy MyApp.war MyDeploymentPlan.xml" - 2. Administrative console -- login to the admin console and click "Deploy New" under Applications - 3. Hot deploy -- copy your archive(s) into the "/deploy" directory. The - hot deploy service will automatically deploy these artifacts. - 4. Maven -- applications can be installed as part of a maven build + 1. Administrative command scripts - + ./bin/gsh deploy/deploy MyApp.war MyDeploymentPlan.xml" + 2. Administrative console - + Login to the admin console and click "Deploy New" under Applications + 3. Hot deploy - + Copy your archive(s) into the "/deploy" directory. + The hot deploy service will automatically deploy these artifacts. + 4. Maven - + Applications can be installed as part of a maven build When you deploy an application using an administrative command, you will need - to supply an administrator's username/password. If you do not specify the username - and password, you will be prompted for them. + to supply an administrator's username/password. If you do not specify the + username and password, you will be prompted for them. ______________________ Configuration ====================== - Commonly modified configuration parameters, such as port numbers, can be set by - editing the file: - - /var/config/config-substitutions.properties + Commonly modified configuration parameters, such as port numbers, can be set + by editing the file: + /var/config/config-substitutions.properties Additional configuration attributes can be updated in the file: - - /var/config/config.xml + /var/config/config.xml Note: The server must not be running when these files are modified. @@ -95,22 +96,24 @@ Security Configuration ====================== - The default administration user/password for the Geronimo Administration Console - and command line deployment tool is system/manager. You can change these defaults - directly from the Geronimo Administration Console by accessing Security -> Users - and Groups and change the user name and password from the Console Realm Users portlet. - - As an alternative, you can make the same changes by editing the - /var/security/users.properties and - /var/security/groups.properties files. - - Access to the var/security directory should be appropriately secured on systems where - you install Geronimo. - - Passwords in users.properties are encrypted by the server. Passwords can be changed - using the Geronimo Administration Console. They can also be changed using a text - editor. While the server is stopped, simply edit the users.properties file. The - password(s) will be encrypted the next time the server is started. + The default administration user/password for the Geronimo Administration + Console and command line deployment tool is system/manager. You can change + these defaults directly from the Geronimo Administration Console by accessing + Security -> Users and Groups and change the user name and password from the + Console Realm Users portlet. + + As an alternative, the same changes can be made by editing the following files: + /var/security/users.properties + /var/security/groups.properties + + Access to the var/security directory should be appropriately secured on + systems where you install Geronimo. + + Passwords in users.properties are encrypted by the server. Passwords can be + changed using the Geronimo Administration Console. They can also be changed + using a text editor. While the server is stopped, simply edit the + users.properties file. The password(s) will be encrypted the next time the + server is started. To prevent potential security exposures, we strongly recommend you update the default user names and passwords on your system. @@ -120,13 +123,14 @@ GShell ====================== - Geronimo provides a command shell environment for executing commands, called GShell. + Geronimo provides a command shell environment for executing commands, + called GShell. - To start a GShell environment, from the directory, execute "./bin/gsh" (unix) - or "bin\gsh" (windows). This will start a GShell command environment. From here, - you can execute Geronimo administrative commands as well as general GShell commands. - Alternatively, you can invoke a GShell command at the same time that you invoke gsh, for - example: + To start a GShell environment, from the directory, execute + "./bin/gsh" (Unix) or "bin\gsh" (Windows). This will start a GShell command + environment. From here, you can execute Geronimo administrative commands as + well as general GShell commands. Alternatively, you can invoke a GShell + command at the same time that you invoke gsh, for example: ./bin/gsh geronimo/stop-server @@ -141,19 +145,21 @@ deploy/install-plugin deploy/assemble - Usage information for any command can be obtained by using the --help option. For example: + Usage information for any command can be obtained by using the --help option. + For example: geronimo/start-server --help - For more information on GShell and GShell commands, see the Geronimo @VERSION@ documentation. + For more information on GShell and GShell commands, see the + Geronimo @VERSION@ documentation. ______________________ Script ====================== - Geronimo provides a number of .sh or .bat scripts that can be used to administer Geronimo - servers. To use most of these scripts, you must first set either the JAVA_HOME - or JRE_HOME environment variable: + Geronimo provides a number of .sh or .bat scripts that can be used to + administer Geronimo servers. To use most of these scripts, you must first set + either the JAVA_HOME or JRE_HOME environment variable: export JAVA_HOME= or @@ -161,7 +167,7 @@ Unix scripts provided by Geronimo (there are .bat equivalents): - geronimo.sh -- used to start and stop servers; either as a foreground or background process. + geronimo.sh -- used to start and stop servers in foreground or background startup.sh -- start a Geronimo server running as a background process shutdown.sh -- stop a running Geronimo server client.sh -- start a Geronimo application client @@ -170,32 +176,33 @@ For example, "./bin/deploy.sh list-modules" - The geronimo.sh and shutdown.sh scripts have multiple sub-commands. Executing the scripts without - any arguments will generate usage information. Executing "help " will generate - usage information for that particular command. + The geronimo.sh and shutdown.sh scripts have multiple sub-commands. Executing + the scripts without any arguments will generate usage information. Executing + "help " will generate usage information for that particular + command. ______________________ Support ====================== - Any problems with this release can be reported to the Geronimo user mailing list - or Jira issue tracker. + Any problems with this release can be reported to the Geronimo user mailing + list or Jira issue tracker. Mailing list archive: - http://mail-archives.apache.org/mod_mbox/geronimo-user/ + http://mail-archives.apache.org/mod_mbox/geronimo-user/ User mailing list: - user@geronimo.apache.org + user@geronimo.apache.org User mailing list subscription: - user-subscribe@geronimo.apache.org + user-subscribe@geronimo.apache.org Jira: - https://issues.apache.org/jira/browse/GERONIMO + https://issues.apache.org/jira/browse/GERONIMO Information concerning security issues and reporting security concerns: - http://geronimo.apache.org/security-reports.html + http://geronimo.apache.org/security-reports.html _______________________________________ Notice Regarding Cryptographic Software @@ -230,3 +237,4 @@ The URL above is a reference to the Apache Geronimo Server source tree for all development (and released) source trees. + Modified: geronimo/server/branches/2.2/RELEASE_NOTES-2.2-SNAPSHOT.txt URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.2/RELEASE_NOTES-2.2-SNAPSHOT.txt?rev=822783&r1=822782&r2=822783&view=diff ============================================================================== --- geronimo/server/branches/2.2/RELEASE_NOTES-2.2-SNAPSHOT.txt (original) +++ geronimo/server/branches/2.2/RELEASE_NOTES-2.2-SNAPSHOT.txt Wed Oct 7 15:50:26 2009 @@ -18,7 +18,7 @@ latest documentation on this release. OR Please see http://cwiki.apache.org/GMOxDOC21/documentation.html for Geronimo -2.1 documentation until Geronimo @VERSION@ documentation is created +2.1 documentation System Requirements @@ -41,19 +41,22 @@ that will mirrors the capabilities of a custom server assembly. GShell -- GShell is a command-line processing environment that can be used for the execution - of Geronimo commands. GShell is an extensible environment and includes support - for editing, command history, and tab completion. +- GShell is a command-line processing environment that can be used for thei + execution of Geronimo commands. GShell is an extensible environment and + includes support for editing, command history, and tab completion. Clustering Support -- WADI can now be used to support clustering of web applications for Geronimo configurations which - use the Tomcat Web Container (WADI support for Jetty was in previous releases). -- Applications can be deployed to administratively-defined groups of Geronimo servers +- WADI can now be used to support clustering of web applications for Geronimo + configurations which use the Tomcat Web Container (WADI support for Jetty was + in previous releases). +- Applications can be deployed to administratively-defined groups of Geronimo + servers Monitoring Console Plugin -- The monitoring console plugin provides monitoring support in the Geronimo admin console. - The monitoring console can gather statistics and performance data from multiple Geronimo - servers and graphically display this data to users. +- The monitoring console plugin provides monitoring support in the Geronimo + admin console. The monitoring console can gather statistics and performance + data from multiple Geronimo servers and graphically display this data to + users. Geronimo @VERSION@ Issues Resolved @@ -93,9 +96,9 @@ - Little-G with Jetty web container, minimal configuration. - Geronimo framework, stripped down Geronimo pluggable framework. -Note: Non-Certified distributions do not contain a complete JavaEE5 stack and so -cannot be certified. Certified distributions can be reconfigured by the user -(such as Tomcat web container with CXF for Web Services). +Note: Non-Certified distributions do not contain a complete JavaEE5 stack and +so cannot be certified. Certified distributions can be reconfigured by the +user (such as Tomcat web container with CXF for Web Services). Supported features