[
https://issues.apache.org/jira/browse/GERONIMO-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546906
]
Jason Dillon commented on GERONIMO-3651:
----------------------------------------
The rc.d stuff simply executes a Groovy script (if it exists) for the given
command. That script is passed in some context to allow it to augment the
sysprops, cl options and other muck as well as do any custom logic/processing.
But for the basic use, the rc.d scripts simply append flags to the JVM, or to
the process and/or set properties for the target JVM. So its very similar to
what is needed to setup the debug muck.... only thing is right now there is no
control over when a script is executed... if its there and has the right name
its run. To make this stuff work, we need to augment it a little to allow the
user to pass in one or more additional scripts to execute (ie. profiles) and
then you cab have a profile for debug, another for optimization, maybe another
for assertions, etc.
Lemme ponder this tonight and I'll see what I can do tomorrow to make this a
reality.
> gshell should make it dead simple to run geronimo with remote debugging
> -----------------------------------------------------------------------
>
> Key: GERONIMO-3651
> URL: https://issues.apache.org/jira/browse/GERONIMO-3651
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: startup/shutdown
> Affects Versions: 2.1
> Reporter: David Jencks
> Assignee: Jason Dillon
>
> we need some options for start-server so g. starts up with debugging. I
> think we should be able to set the port and suspend as persistent options in
> the environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
