Create a robust shell wrapper for launching Application jar in the embedded mode about orville HOT 4 CLOSED

I would put this as a very low priority. Most of those startup scripts do a lot of environment initialization and checking before executing the target, which isn't needed in our instance (and when it is, it's deployment specific). If this sort of robustness is absolutely needed, I would say a WAR deployment is better early on.

from orville.

Well, I'd still would like may be simpler wrapper script included in the distribution to be able to run as init.d or launchd daemon :-) Not the highest priority, agree, but things like that would make the product production ready - whatever that means. Also, if the product is looked at and adopted by the community, it would be nice that folks drive those kind of issues.

from orville.

Yeah, this should be community driven. The first problem you run into when writing init scripts is deciding what type you're going to write and support. SYSV? Upstart? Windows Service? OSX Service? I would imagine that most folks that administer systems would know how to create such a script (or find out how) and could contribute something back.

from orville.

Possibly look at the Gradle's application plugin to do this for us

from orville.