Comment 6 for bug 576784

I'm not sure I understand your point. Isn't that the way it works now? This is my understanding of the script:

1.- If /war dir exists it is copied to destination war_path otherwise create empty war_path and war_path/WEB-INF.
2.- A standard web.xml file is copied to war_path/WEB-INF/ if there isn't one already there.
3.- /app is copied to war_path/WEB-INF/application/.
4.- /conf is copied to war_path/WEB-INF/classes/.
5.- Play jar files are copied into war_path/WEB-INF/lib.
6.- Framework templates are copied to war_path/WEB-INF/framework/templates
7.- Modules are copied to war_path/WEB-INF/modules/
8.- Framework resources are copied to war_path/WEB-INF/resources/messages

So the WEB-INF directory is already being disturbed quite a bit. What's the point in giving the user the option to drop a webapp in /war and then completely ignore the contents of their lib and classes directories? In the simplest of examples, with a brand new empty Play app and a working webapp in /war, after running this script the web.xml will be preserved but the webapp won't work at all without those other dirs. How was this supposed to work in the first place?