Page History

...

• Changing widgetset/theme config currently requires a server restart
  
  • most likely AdmincentralUIProvider injected instance in servlet is not refreshed when module configuration changes
  • don't store definition references, only module reference and query dynamically for configured definitions 
• Is configuration really where we want widgetset config to be?
  
  • Since developers should now use their widgetset extending ours
  • Currently they would startup, change widgetset name in config, then restart
  • e.g. magnolia / project.properties, module descriptors?
  • ee-bundle might need to configure default widgetset differently too

Review 2013.08.29

• We do the widgetset-at-bundle-level step
• We also do the renames/reorganizes in the UI
• Speaks for a magnolia property
• Auto-discovery?
  
  • Should we do it as a guideline?
  • It's helpful for others
    
    • or through an archetype?
• Performance (hudson)
  
  • full-fledged gwt compilation in bundle build
  • we split this out
    
    • depends on ui, modules
    • is depended upon by bundle
    • we use profiles, or subset of the reactor
• We have yet to decide what we do for 5.1/5.2
  
  • it's better if it's one significant step, but it may well require too much time vs. 5.1 stories
  • widgetset/theme in configuration is in master but was not released (except in 5.1-alpha1)
    • We now want to use magnolia properties instead
      
• My proposal
  
  • We may do as little as changing this configuration for 5.1, so that we don't ship something we know we will remove
  • everything else is for 5.2 then