[MGNLBACKUP-39] Remvoe obsolete repository_xml from backup Created: 13/Jul/11  Updated: 29/Mar/22  Resolved: 04/Nov/15

Status: Closed
Project: Backup
Component/s: None
Affects Version/s: 1.1.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Team: Nucleus

 Description   
  • The content of the file is restored into repository.xml when one doesn't exist.
  • However, the backup is made from magnolia.repositories.jackrabbit.config instead of from magnolia.repositories.config
  • and since svn #r16343 and use of AbstractBasicExecutable to launch restore, repository.xml is required to exist prior starting the restore itself

So content of the file is incorrect and is actually never used during restore.

The file should be either completely removed or it should be named correctly (template for creation of the workspaces) and should be restored using the correct name.



 Comments   
Comment by Nils Breunese [ 10/Aug/11 ]

Typo in this issues' title: Remvoe -> Remove.

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 Sun Feb 11 23:24:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.