Update mechanism improvements (MAGNOLIA-5529)

[MAGNOLIA-1806] Refactoring / cleanup of the bootstrap classes methods Created: 31/Oct/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

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:
dependency
is depended upon by MAGNOLIA-1795 Review bootstrap install tasks Closed
is depended upon by MAGNOLIA-1945 Bootstrap tasks should support backup Closed
is depended upon by MAGNOLIA-1785 Write tests for various bootstrap pro... Closed
relation
is related to MAGNOLIA-2245 Review and suppress usage of deprecat... Closed
is related to MAGNOLIA-1842 Default bootstrap behaviour should be... Closed
is related to MAGNOLIA-2245 Review and suppress usage of deprecat... Closed
Template:
Date of First Response:

 Description   

The whole Bootstrap mechanism should be reviewed. There are currently multiple places where bootstrap is used:

  • Bootstrapper (used to bootstrap data when installing webapp)
  • BootstrapTasks (they use the deprecated ModuleUtil methods)
  • DataImporter

All of them here and there do the same thing but do not use a common API, e.g. to:

  • resolve the target node out of the filename
  • not all support tar.gz files instead of xml files
  • etc.

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: MAGNOLIA-1842.

Comment by Magnolia International [ 09/Dec/08 ]

Now what we started progress on MAGNOLIA-2245, we might consider this again !

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.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:30:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.