[BUILD-193] Maintenance profile doesn't work on multi-module projects Created: 17/Dec/14  Updated: 04/May/15  Resolved: 17/Dec/14

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: POMs 31

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
Template:
Acceptance criteria:
Empty
Date of First Response:

 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:



 Comments   
Comment by Magnolia International [ 17/Dec/14 ]

Documentation updated. Note that for this to work with parent pom 30, you can already remove the file and set the property instead.

Comment by Philip Mundt [ 04/May/15 ]
[WARNING] The requested profile "magnolia-maintenance-mode" could not be activated because it does not exist.
Generated at Sun Feb 11 23:39:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.