[MAGNOLIA-6723] Improve Module installation behavior: When bootstraps are already there allow skipping bootstrapping Created: 18/Jul/16 Updated: 01/Dec/22 Resolved: 01/Dec/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | modulemechanism |
| Affects Version/s: | 5.4.7 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christian Ringele | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | support, to-specify, to-verify | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| 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: | |||||
| Story Points: | 13 | ||||
| Team: | |||||
| Description |
|
I was helping 3 weeks in Support and have seen this problem there a couple of time only in these three weeks. The problem:
Also in development/training: Effect:
Both are situations, where all what is needed is that the system starts up again. Solution:
I thin both are achievable with not much effort. Cheers |
| Comments |
| Comment by Christian Ringele [ 19/Jul/16 ] |
|
A typical Project situation: TypialProjectSituation.png Old project checked out, deployed fist time, uuid conflict. Would be much easier to solve being able to start the system and drop jcr queries for searching the node with this uuid. Instead of searching trough all the bootstrap files in the modules. -> update: |
| Comment by Jan Haderka [ 04/Aug/16 ] |
|
Actually the analysis above is incorrect. |