The current magnolia-maintenance-mode profile doesn't work with multi-module projects, at least not anymore since we moved to Maven 3.
The reason is, it's activated by the presence of a file, and since Maven 3, this file is expected to be in the root of the module rather than the root of the reactor.
I was hoping to use the directory plugin to determine the "real" root of the reactor, but unfortunately, <file> can't be interpolated with properties set at runtime.

Since all the profile ever did was set magnolia.public.maintenance property, I'm proposing removing the profile altogether, and updating our documentation instead:

• http://wiki.magnolia-cms.com/display/DEVINT/Maintenance+mode+and+releases
• http://wiki.magnolia-cms.com/display/DEV/Maven+Parent+POMs