[MGNLUI-2482] Allow setting Vaadin production mode via magnolia.properties Created: 05/Aug/13 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | next | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Description |
|
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. |