<commit_before>Release Notes -- Apache Geronimo -- Version 1.0

Geronimo URLs
-------------
Home Page:     http://geronimo.apache.org/
Downloads:     http://geronimo.apache.org/downloads.html
Documentation: http://geronimo.apache.org/documentation.html
Mailing Lists: http://geronimo.apache.org/mailing.html
Source Code:   http://geronimo.apache.org/svn.html
Bug Tracking:  http://issues.apache.org/jira/browse/GERONIMO
Wiki:          http://wiki.apache.org/geronimo


System Requirements
-------------------
You need a platform that supports the Sun JDK 1.4.2.  CORBA
support requires a Sun Java 1.4.2 VM (specifically 1.4.2_08
or a higher 1.4.2_* release).

Most testing has been done on Linux, Mac OS X, and Windows.


Installing & Starting Geronimo
------------------------------
To install, simply unpack the .zip (Windows) or tar.gz (Unix) file 
containing Geronimo.

Documentation is included in the docs directory in your unpacked server.

If you wish to modify the default ports that 
Geronimo will use, edit the file var/config/config.xml in your 
Geronimo directory.

Geronimo comes with batch and script files to control server start 
and stop functions.  To see usage examples simply type geronimo.bat 
or geronimo.sh command as appropriate for your platform.  It is 
necessary to set JAVA_HOME to the copy of your Sun 1.4.2 JDK/JRE 
prior to executing the command.  Here is an example:

export JAVA_HOME=/directory_to_the_JRE/
bin/geronimo.sh

The command will display help text instructing you as to how to start 
and stop the Geronimo server.

If you prefer to start the server without a script file you can simply type: 

java -jar bin/server.jar

Once the server has started, you can access the administration console
at http://localhost:8080/console/ . The default user name is "system" and
the default password is "<PASSWORD>".


Administration Console Security Configuration
---------------------------------------------
The default administration user/password for the admin console and
deployment is system/manager.  To change this edit the
var/security/users.properties and var/security/groups.properties
files.


Deploying Applications
----------------------
Geronimo comes with deploy scripts and batch files to deploy J2EE
modules or applications. Alternatively, to deploy a J2EE module or 
application, start Geronimo and then run (for example):

   java -jar bin/deployer.jar deploy my-web-app.war [deploy plan]

You will need to use the username "system" and password "manager"
unless you customized those during the install process.  The
deployment plan argument is optional -- you can pack a deployment
plan into the application module, provide it on the command line,
or in some cases omit it entirely.

For more information on the commands and options supported by the
deploy tool, run

   java -jar bin/deployer.jar help [command]


Other Deployment Options
------------------------
As an alternative to the command-line deployer, you can copy
application modules into the geronimo/deploy/ directory and the
hot deployer service will deploy them automatically.  The
command-line deployer has some advantages, as it will output any
deployment errors to its own console rather than just the server
log, but either method will generally work.

Additionally, Geronimo provides a Maven plugin that can deploy
applications to Geronimo as part of a Maven build.


Future Road Map at a Glance
---------------------------
http://issues.apache.org/jira/browse/GERONIMO?
      report=com.atlassian.jira.plugin.system.project:roadmap-panel

  (the above URL must be all on one line)


Significant Changes Since the M5 Release
----------------------------------------
 * the ConfigID format has been updated in anticipatation of future
   enhancements.  Application plans that include configIds of
   configurations included in Geronimo M5 and earlier will require
   modifications.  See the Wiki at http://wiki.apache.org/geronimo
   for more information.
 * More functionality and new look and feel for the Administrative
   Console (http://localhost:8080/console/)
 * Added HTTP session clustering to the Tomcat configuration
   included with Geronimo
 * Hot Deploy by copying your deployment artifact to the deploy/
   directory
 * Ability to run the deploy tool from a machine other than the
   application server (remote deployment)
 * Packages that represented experimental, pre-release or obsolete
   versions were removed.<commit_msg>Updated 1.0 Release Notes<commit_after>Release Notes -- Apache Geronimo -- Version 1.0

Geronimo URLs
-------------
Home Page:     http://geronimo.apache.org/
Downloads:     http://geronimo.apache.org/downloads.html
Documentation: http://geronimo.apache.org/documentation.html
Mailing Lists: http://geronimo.apache.org/mailing.html
Source Code:   http://geronimo.apache.org/svn.html
Bug Tracking:  http://issues.apache.org/jira/browse/GERONIMO
Wiki:          http://wiki.apache.org/geronimo


System Requirements
-------------------
You need a platform that supports the Sun JDK 1.4.2.  CORBA
support requires a Sun Java 1.4.2 VM (specifically 1.4.2_08
or a higher 1.4.2_* release).

Most testing has been done on Linux, Mac OS X, and Windows.


Installing & Starting Geronimo
------------------------------
To install, simply unpack the .zip (Windows) or tar.gz (Unix) file 
containing Geronimo.

Documentation is included in the docs directory in your unpacked server.

If you wish to modify the default ports that 
Geronimo will use, edit the file var/config/config.xml in your 
Geronimo directory.

Geronimo comes with batch and script files to control server start 
and stop functions.  To see usage examples simply type geronimo.bat 
or geronimo.sh command as appropriate for your platform.  It is 
necessary to set JAVA_HOME to the copy of your Sun 1.4.2 JDK/JRE 
prior to executing the command.  Here is an example:

export JAVA_HOME=/directory_to_the_JRE/
bin/geronimo.sh

The command will display help text instructing you as to how to start 
and stop the Geronimo server.

If you prefer to start the server without a script file you can simply type: 

java -jar bin/server.jar

Once the server has started, you can access the administration console
at http://localhost:8080/console/ . The default user name is "system" and
the default password is "<PASSWORD>".


Administration Console Security Configuration
---------------------------------------------
The default administration user/password for the admin console and
deployment is system/manager.  To change this edit the
var/security/users.properties and var/security/groups.properties
files.


Deploying Applications
----------------------
Geronimo comes with deploy scripts and batch files to deploy J2EE
modules or applications. Alternatively, to deploy a J2EE module or 
application, start Geronimo and then run (for example):

   java -jar bin/deployer.jar deploy my-web-app.war [deploy plan]

You will need to use the username "system" and password "<PASSWORD>"
unless you customized those during the install process.  The
deployment plan argument is optional -- you can pack a deployment
plan into the application module, provide it on the command line,
or in some cases omit it entirely.

For more information on the commands and options supported by the
deploy tool, run

   java -jar bin/deployer.jar help [command]


Other Deployment Options
------------------------
As an alternative to the command-line deployer, you can copy
application modules into the geronimo/deploy/ directory and the
hot deployer service will deploy them automatically.  The
command-line deployer has some advantages, as it will output any
deployment errors to its own console rather than just the server
log, but either method will generally work.

Additionally, Geronimo provides a Maven plugin that can deploy
applications to Geronimo as part of a Maven build.


Future Road Map at a Glance
---------------------------
http://issues.apache.org/jira/browse/GERONIMO?
      report=com.atlassian.jira.plugin.system.project:roadmap-panel

  (the above URL must be all on one line)


Late Release News (not in RELEASE-NOTES-1.0.txt in build)
---------------------------------------------------------
Just as the Geronimo Release was being prepared a report was made about a 
potential security issue when using the Jetty Web Conatiner.  The issue was noted 
on Jetty 5.1.9 which used by geronimo 1.0, which allows a crafted URL to access the 
contents of a WEB-INF directory if the server is running on a Windows platform.   
This issue is fixed in Jetty 5.1.10 and will be provided in Geronimo 1.0.1 which will
be available in the near future.


Significant Changes Since the M5 Release
----------------------------------------
 * the ConfigID format has been updated in anticipatation of future
   enhancements.  Application plans that include configIds of
   configurations included in Geronimo M5 and earlier will require
   modifications.  See the Wiki at http://wiki.apache.org/geronimo
   for more information.
 * More functionality and new look and feel for the Administrative
   Console (http://localhost:8080/console/)
 * Added HTTP session clustering to the Tomcat configuration
   included with Geronimo
 * Hot Deploy by copying your deployment artifact to the deploy/
   directory
 * Ability to run the deploy tool from a machine other than the
   application server (remote deployment)
 * Packages that represented experimental, pre-release or obsolete
   versions were removed.
{'fraction_non_alphanumeric': 0.10222970130416491, 'fraction_numerical': 0.008203618005889778, 'mean_word_length': 3.1779437609841827, 'pattern_counts': {'":': 0, '<': 6, '<?xml version=': 0, '>': 6, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 2}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4971451', 'n_tokens_mistral': 2557, 'n_tokens_neox': 2420, 'n_words': 1191}