You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2010/04/19 21:43:51 UTC
[jira] Commented: (GERONIMO-5213) Review Geronimo 3.0 commands need
a thorough review
[ https://issues.apache.org/jira/browse/GERONIMO-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858655#action_12858655 ]
Jarek Gawor commented on GERONIMO-5213:
---------------------------------------
Cleaned up the geronimo, client, deploy, startup, and shutdown scripts in revision 935712. They pretty much work just like they used in (as in Geronimo 2.2)
> Review Geronimo 3.0 commands need a thorough review
> ---------------------------------------------------
>
> Key: GERONIMO-5213
> URL: https://issues.apache.org/jira/browse/GERONIMO-5213
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands
> Affects Versions: 3.0
> Reporter: Kevan Miller
> Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> The current set of Geronimo commands (geronimo, deploy, start, stop, shutdown, admin, client) need to be reviewed for functionality. Mostly, they are adopting gshell syntax/semantics. There needs to be a thorough review that the new set of commands are providing all of the features/functions that users are currently using.
> I think having a single set of commands rather than the duplicate commands (old and newer gshell-based commands) is good. There should be documentation on how to migrate from the old environment to the new. For example, for people using JAVA_OPTS / GERONIMO_OPTS how do they move to the new geronimo command?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.