Let me know if you would like the full stack trace. engine-spring.xml is explicitly referenced in OG-Examples/build.xml as well as start-jetty.(bat|sh). ‘find . -name “engine-spring.xml”’ from OG-Platform yields no results. Is it possible that this was missed in a git push?

On an unrelated note, is it possible to allow text formatting in Vanilla to allow better formatting for code snippets/ant output when posting to the forum? I know Bjarne Stroustrup likes using non-fixed-width fonts for code formatting, but I think it looks best monospaced.

I’m currently introducing a whole new config system to master. This has caused various things to break, including the examples jetty-debug task. I’m looking into fixing that at the moment. More documentation will appear on the config rewrite in the next week or so. Stay tuned…

“ant jetty” and “ant jetty-debug” should now be working again with my latest push. Note that both rely on the web-engine directory being located under the OG-Examples directory. If you have a checked out source tree, you need to change “fullstack-example.properties” to “fullstack-example-dev.properties” in the build.xml (I hope to improve this).

I think you’re right. The reason they’re like that is that we tend to run more complex configurations than the examples locally on machines with lots of RAM, so it just slipped through into the examples. The Windows installer, for example, uses a percentage of available RAM (although it struggles if you try to run e.g. R, and Engine and Bloomberg in 2GB, which is why we haven’t released a 32-bit installer). I’ve opened and assigned a JIRA issue to fix it for the next point release. Thanks for reporting it!