[MAGNOLIA-1767] update mechanism: manual tasks Created: 11/Oct/07 Updated: 23/Jan/13 Resolved: 17/Nov/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | updatemechanism |
| Affects Version/s: | 3.1 M3 |
| Fix Version/s: | 3.5 RC1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | 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
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Some tasks are manual tasks the user should do himself. The UI should tell him what he has to do and ask him to confirm the changes |
| Comments |
| Comment by Magnolia International [ 23/Oct/07 ] |
|
The WarnTask already provide the information. |
| Comment by Magnolia International [ 23/Oct/07 ] |
|
We will have a set of tasks which are "blocking" other tasks. They could check conditions, for instance if web.xml or repositories.xml are up-to-date, and until those conditions are met, other tasks would not be available. |
| Comment by Magnolia International [ 28/Oct/07 ] |
|
Solving this with "Condition"s. Each Delta can provide Conditions, which have to be matched for the update to be performed. Should one of the conditions needed by a delta not be met, no install/update will take place, even for other modules. |
| Comment by Magnolia International [ 17/Nov/07 ] |
|
done. see comments above. |