geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "erik daughtrey (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1192) Installer should create a config.xml for the target install
Date Mon, 12 Dec 2005 03:20:08 GMT
    [ ] 

erik daughtrey commented on GERONIMO-1192:

The patch uploaded today contains:

1. changes to config.xml in assemblies/j2ee-installer/src/var/config so that it has variables
to be replaced by
the installer for enabling various features.

2. A new set of code in modules/installer-support which extends the izpack functionality to
allow additional control of the installation work flow. 
     a) enables code to check if both jetty and tomcat are selected
     b) enables code to do variable manipulation and set variables in config.xml based on
the packs selected.

3. Changes to assemblies/j2ee-installer/src/geronimo-izpack.xml to enable a few variables
and enable the extensions made available by modules/installer-support.

4. Changes to assemblies/j2ee-installer/src/izpack-user-input.xml to add an error panel to
be displayed if both tomcat and jetty are selected and to enable a panel at the end of configuration
to give the operator a chance to review the config.  Also the last panel is a trigger for
the extension code to do some work.

> Installer should create a config.xml for the target install
> -----------------------------------------------------------
>          Key: GERONIMO-1192
>          URL:
>      Project: Geronimo
>         Type: New Feature
>   Components: installer
>     Versions: 1.0-M5
>  Environment: Installer runtime
>     Reporter: erik daughtrey
>     Assignee: John Sisson
>      Fix For: 1.0
>  Attachments: installer-200512111301.patch, installer_1192_200512080036.patch
> DJ - "This could be done by adding bits associated with each configuration, or by removing
chunks from a 'universal' config.xml for the configuations we didn't install."

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message