Update mechanism improvements
(MAGNOLIA-5529)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | modulemechanism |
| Affects Version/s: | 3.5.4 |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Magnolia International |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
This is utterly important for conditions. Currently only conditions which are executable before the repository is started are supported while one would like to use the node registry. |
| Comments |
| Comment by Magnolia International [ 10/Jul/08 ] |
|
Approaching the 3.6 release, we went around this (or had the idea to, at least?) by using a failing task. If exceptions are handled properly ( |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |