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.
This sounds great. I don't think it would be much of a change to make this happen.
Of course, windows service and init.d are also useful. I think both proposals are worth pursuing
This would be a great addition. Jeff
