[magnolia-dev] [JIRA] (BUILD-193) Maintenance profile doesn't work on multi-module projects

[on behalf of Grégory Joseph]

Grégory Joseph created BUILD-193 Maintenance profile doesn't work on multi-module projects Issue Type: Bug Assignee: Grégory Joseph Created: 17/Dec/14 5:33 PM Description: 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 Fix Versions: POMs 31 Project: Build Priority: Neutral Reporter: Grégory Joseph Security Level: Public

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

---

----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------