[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: |
|
||||
| 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. 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.
|