[ http://issues.apache.org/jira/browse/GERONIMO-1038?page=all ]

Aaron Mulder updated GERONIMO-1038:
-----------------------------------

      Component: ActiveMQ
                 application client
                 buildsystem
                 common
                 connector
                 console
                 CORBA
                 core
                 databases
                 dependencies
                 deployment
                 eclipse-plugin
                 gbuild
                 general
                 installer
                 JVM-compatibility
                 kernel
                 mail
                 management
                 naming
                 OpenEJB
                 sample apps
                 security
                 ServiceMix
                 specs
                 startup/shutdown
                 TCK
                 Tomcat
                 transaction manager
                 twiddle
                 usability
                 web
                 webservices
                 xdoclet-plugin
    Fix Version: Wish List
        Version: 1.0-M5

I can't see assigning an uber-issue like this to any specific release.  Maybe 
you can create specific subtasks to assign to individual releases?

> Improve Serviceability of Geronimo
> ----------------------------------
>
>          Key: GERONIMO-1038
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1038
>      Project: Geronimo
>         Type: New Feature
>   Components: ActiveMQ, application client, buildsystem, common, connector, 
> console, CORBA, core, databases, dependencies, deployment, eclipse-plugin, 
> gbuild, general, installer, JVM-compatibility, kernel, mail, management, 
> naming, OpenEJB, sample apps, security, ServiceMix, specs, startup/shutdown, 
> TCK, Tomcat, transaction manager, twiddle, usability, web, webservices, 
> xdoclet-plugin
>     Versions: 1.0-M5
>  Environment: All
>     Reporter: Matt Hogstrom
>      Fix For: Wish List

>
> Currently Geronimo requires significant intervention on the part of the user 
> when applying fixes to a Geronimo server instance.  The interventions can 
> range from something as simple as reading a set of iinstructions and making a 
> manual change to haveing to rebuild the entire server to introduce a required 
> fix into their environment.  Geronimo needs a servicebility strategy that 
> will allow fixes to be introduced to the users environment in the least 
> disruptive way.  This involves a number of elements like a fix installer, 
> ability to know what service level Geronimo is at, attention to 
> serialVersionUID issues, etc.  
> This JIRA highlights a significant barrier to wide range adoption of Geronimo 
> for users of a commercial nature in terms of disruption to production use 
> when some fixes are introduced into the environment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to