Dave Colasurdo wrote:

I agree the current behavior is appropriate for a developer. I was thinking more about end users. Similar to your suggestion, should we consider adding an option to the startup.sh|bat script to put the process in background? Actually, I'm wondering if the default behavior (startup.sh|bat w/o any options) should be geared toward end users and would run the process in background. And specifying the option (-foreground) would allow the process to be run in the current window for developers.

As you're doing it....could we (you ;)) follow Tomcat's approach where start starts an instance in the background and run runs it in the foreground? The default option would list the available options.

Of course, windows service and init.d are also useful. I think both proposals are worth pursuing

+1

Jacek

Reply via email to