I have been working on updating our Elastic Beanstalk jetty integration and updating it to Jetty 9 and wanted to point out an assumption in the core beanstalk scripts related to clean.
As a part of the appdeploy process several scripts are run, one of which smokes the entirety of the contents of the webapps directory.
The theory here being that it wants a clean slate to then copy in the contents of the application into, however the issue is that now with our combined directory we have ROOT.d directories and perhaps content.xml files mixed in the webapps directory, and the hooks that beanstalk provides for an application to influence the container have already run at this point. So in my app configuration I am creating a ROOT.d directory, configuring my application, dropping in an extra context.xml file which is all promptly deleted before my application is deployed.
Now...beanstalk is incredibly configurable, and I can certainly replace this clean.sh script (which I will have to) but it is indicative of a thought process that we should consider in this discussion.
Perhaps we should have a community google hangout on this topic at some point, that might be rather fun.
jesse