I was a little too eager to "properly" disable Clover (as per BUILD-110), and realized this actually did not work for submodules of reactor projects.

What happens is that the additionalReleaseProfiles is used to configure the release plugin... in the parent poms. Setting that property in a submodule is unfortunately too late.

Proposed fix:

• enable the gwt-production-mode profile via additionalReleaseProfiles from the parent (even if the profile is defined in a submodule)
• disable clover the old-fashioned way via pluginManagement in magnolia-ui-vaadin-common-widgets and magnolia-ui-vaadin-widgetset