[MAGNOLIA-4700] Versioning breaks when using multiple repositories within one Magnolia instance Created: 30/Nov/12  Updated: 02/Jul/18  Resolved: 02/Jul/18

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.5
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
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

 Description   

During versioning CopyUtil uses clone() to transfer data from source workspace to mgnlVersion. Since workspace.clone() supports cloning only between workspaces of the same repository this operation breaks when source and destination workspaces are not in same repository. See attached stacktrace for details.

One possible solution would be to use export/import instead of cloning for transfer.



 Comments   
Comment by Jan Haderka [ 02/Jul/18 ]

fixed in 5.5 with intro of logical mapping for mgnl* workspaces and their autocreation for each configured responsibility.

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