Just out of interest... Why do we use the embedded jetty for development purposes and then shipping on tomcat?
Why aren't we using embedded tomcat for development purposes? Does it matter? Is there any reason we don't ship a JAR with embedded tomcat and remove the system dependency on tomcat? It cleans up the binary packages to no end. Jenkins operates like this with the embedded version of jetty, their installation is essentially just init script calling a JAR with a bunch of parameters: https://github.com/jenkinsci/jenkins/tree/master/debian Spring-boot is also follows a similar approach with tomcat embedded http://spring.io/blog/2014/03/07/deploying-spring-boot-applications. Why do we ship on a system version of tomcat rather than an embedded version all contained within a JAR? Is there any specific reason why we used tomcat over jetty for production purposes? Regards, Ian
