Update mechanism improvements
(MAGNOLIA-5529)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | updatemechanism |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | cleanup | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Description |
|
The whole Bootstrap mechanism should be reviewed. There are currently multiple places where bootstrap is used:
All of them here and there do the same thing but do not use a common API, e.g. to:
Also the usage of the ImportUUIDBehavior is sometime inconsistent used. We should probably use ImportUUIDBehavior.IMPORT_UUID_COLLISION_THROW as a default behaviour. In general we should introduce a main BootstrapUtil class that is commonly used by all classes mentioned above. |
| Comments |
| Comment by Vivian Steller [ 10/Dec/07 ] |
|
The ImportUUIDBehavior was changed recently and should still be considered: |
| Comment by Magnolia International [ 09/Dec/08 ] |
|
Now what we started progress on |
| Comment by Magnolia International [ 11/Dec/08 ] |
|
Will do at least some cleanup for 4.0 |
| Comment by Magnolia International [ 26/Jan/09 ] |
|
Since 4.0, classes have been moved to the info.magnolia.importexport package, but the api should still be cleaned up and improved. |
| 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. |