hi,
since you are discussing changes to the jetty start.ini / start.jar I would like to propose a few things:
- The generated classpath is now gigantic, including one by one every single jar inside /lib.
This is no longer necessary as modern VMs support the "*" wildcard for the classpath.
We use it successfully at work.
This would help as on UNIX systems you are stuck with "ps -ef" and the output for jetty is so long at the moment that you can't see all of it.
- Do we really need start.jar / a java launcher?
It would be cool to be able to start jetty just with a script so that there is no launcher java process.
With the classpath change described above it should be pretty straightforward.
It is sometimes confusing to have two processes running, one doing apparently very little (it seems to linger around after starting jetty but does not seem to provide auto-restart of jetty).
- Automatic start up on UNIX.
As far as I know on UNIX configuring processes to start automatically can be done in a number of ways, all of them confusing / unclear unless you are a UNIX guru / sysadmin.
In the Jetty documentation there doesn't seem to be a clear indication of how to achieve that.
I think it would be very helpful having a simple script under "/bin" that just installs Jetty to start automatically when the machine reboots.
- Use of variable JAVA in current script instead of JAVA_HOME
This is a minor one but the standard in the Java world is JAVA_HOME (pointing to the root installation folder of Java) and not JAVA pointing to the java executable.
Hope the above makes sense, apologies if I have missed something obvious in the documentation, in that case I deserve a loud RTFM.
Many thanks,
Michele
