You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org> on 2005/10/05 14:39:55 UTC
[jira] Created: (GERONIMO-1038) Improve Serviceability of Geronimo
Improve Serviceability of Geronimo
----------------------------------
Key: GERONIMO-1038
URL: http://issues.apache.org/jira/browse/GERONIMO-1038
Project: Geronimo
Type: New Feature
Environment: All
Reporter: Matt Hogstrom
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
[jira] Updated: (GERONIMO-1694) Improve Serviceability of Geronimo
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1694?page=all ]
Dain Sundstrom updated GERONIMO-1694:
-------------------------------------
Component: kernel
Fix Version: 1.1
Assign To: Dain Sundstrom
> Improve Serviceability of Geronimo
> ----------------------------------
>
> Key: GERONIMO-1694
> URL: http://issues.apache.org/jira/browse/GERONIMO-1694
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: kernel
> Environment: All
> Reporter: Matt Hogstrom
> Assignee: Dain Sundstrom
> Fix For: 1.1
>
> 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
[jira] Updated: (GERONIMO-1038) Improve Serviceability of Geronimo
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Updated: (GERONIMO-1694) Improve Serviceability of Geronimo
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1694?page=all ]
Dain Sundstrom updated GERONIMO-1694:
-------------------------------------
Assign To: (was: Dain Sundstrom)
> Improve Serviceability of Geronimo
> ----------------------------------
>
> Key: GERONIMO-1694
> URL: http://issues.apache.org/jira/browse/GERONIMO-1694
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: kernel
> 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
[jira] Updated: (GERONIMO-1694) Improve Serviceability of Geronimo
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1694?page=all ]
Matt Hogstrom updated GERONIMO-1694:
------------------------------------
Fix Version: Wish List
(was: 1.1)
Moving to Wish List as this is an Uber Item as Aaron has indicated.
> Improve Serviceability of Geronimo
> ----------------------------------
>
> Key: GERONIMO-1694
> URL: http://issues.apache.org/jira/browse/GERONIMO-1694
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: kernel
> Environment: All
> Reporter: Matt Hogstrom
> Assignee: Dain Sundstrom
> 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