geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Geronimo Wiki] Update of "Building an Installer" by AaronMulder
Date Sat, 14 May 2005 15:12:55 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Geronimo Wiki" for change notification.

The following page has been changed by AaronMulder:
http://wiki.apache.org/geronimo/Building_an_Installer

------------------------------------------------------------------------------
       * {{{system-database-plan.xml}}} -- hostname (localhost) and port for Derby network
access (1527) [`PlanServerHostname`, `PlanDerbyPort`]
       * {{{system-jms-plan.xml}}} -- hostname, port for ActiveMQ (localhost:61616) [`PlanServerHostname`,`PlanActiveMQPort`]
       * {{{system-plan.xml}}} -- port for RMIRegistry (1099), server host name (localhost)
[`PlanServerHostname` and `PlanNamingPort`]
-    * substitute variables for username and password in {{{var/security/users.properties}}}
and {{{var/security/groups.properties}}} (e.g. overwrite with `${SecurityDefaultUser}=${SecurityDefaultPassword}`
and `admin=${SecurityDefaultUser}`)
-  * The IzPack installer config files are copied into the `assembly/target/installer` directory
during the assembly build, with certain variable substitution performed.
+  * The IzPack installer config files and all necessary Geronimo files are copied into the
`assembly/target/installer` directory during the assembly build, with certain variable substitution
performed.
-    * You may want to update maven.xml to have the correct version number for the most recent
release notes file.  There's probably a better place to store this.
+    * You may want to update maven.xml to have the correct version number for the most recent
release notes file (Jelly variable `ReleaseNotesVersion`).  There's probably a better place
to store this.
     * The installer configuration is not really optimal
-      * The settings need to be split into 3 screens -- as is if you install everything both
of the current screens overflow and some fields are just invisible
       * The same default configurations are always marked to be started (fortunately I think
all of them are in required packages)
       * It's not clear what would happen in the event of a port collision since the installer
attempts to run the server in order to install to it
       * It individually deploys each of the up to 17 possible configurations (using the slow
one-off deployer), which takes a pretty long time -- compare to the assembly module which
starts the server after 3 or 4 steps, does everything else against the running server, then
shuts it down.

Mime
View raw message