FYI, I've gotten my POC using GShell for this ready... I'm planning
on merging the changes into server/trunk today, though I'm not going
to hook it up to the default assemblies just yet. Instead I'm going
to create a new assembly to allow folks to play with it first and
then we can talk about making it the default. More email on how all
this stuff works in a wee bit.
Cheers,
--jason
On Jul 19, 2007, at 7:28 AM, Jeff Genender wrote:
Lets let Jason chime in here as I think he volunteered to stitch a lot
of this together.
Jeff
Donald Woods wrote:
Could we use Jakarta commons-launcher, which uses a subset of ANT?
We'd probably have to make a few changes, so it would use the
existing
manifest settings in the server/client.jar and to handle our multiple
server instance directory structure.....
-Donald
Jeff Genender wrote:
Hi,
As we move forward and we integrate with more and more 3rd party
products, we will need the ability to be able to change an
environment
variable through a plugin, or add a commandline JAVA_OPTS, etc.
Currently our startup scripts call the setjavaenv.sh to set
environment
properties. It would really be nice to have the ability to have a
"scripts" directory, where all of the scripts get executed before
Geronimo is launched. Why do we want this?
As we grow in our plugins, they will need to set environment or java
options set before running G. They may also have a need to start
or run
other outside processes that are not a part of G.
It would be great to allow plugins to install an rc script that gets
executed to do activities before and perhaps after G is run?
I would propose we create a scripts directory under bin or under var
that could be similar to init.d, and have it called with start/stop,
etc. This way plugins can install specific scripts in these
directories
for execution.
Thoughts?
Jeff
