We should be able to switch the productionMode flag of Vaadin based on the value of our magnolia.develop property rather than have the two independent mechanism (web.xml for Vaadin, magnolia.properties for everything else)

It looks like this should be doable by override com.vaadin.server.VaadinServlet#createDeploymentConfiguration in AdmincentralVaadinServlet and perhaps have it use another implementation of com.vaadin.server.DeploymentConfiguration.

This sounds easy - but of course needs to be tested.
Ideally, this could be implemented using IoC if MAGNOLIA-4396 was fixed.