[MGNLDAM-84] MigrationTask DMS to DAM has to check for exsitstence of DMS workspace Created: 14/Jan/13  Updated: 11/Feb/13  Resolved: 15/Jan/13

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Blocker
Reporter: Daniel Lipp Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLSTK-1042 STK should no longer depend on DMS Closed
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   

Until recently DMS was always around (brought in by STK). As this is no longer the case, the migration tasks in DAM have to check whether such a workspace is around to avoid exceptions like:

[INFO] [talledLocalContainer] 2013-01-14 10:35:30,206 INFO tup.migration.MoveDataRepositoryToDamMigrationTask: Start to move data from 'dms' to DAM repository.
[INFO] [talledLocalContainer] 2013-01-14 10:35:30,207 ERROR info.magnolia.module.InstallContextImpl : > Unable to perform Migration task Migration task: Migrate DMS content to DAM
[INFO] [talledLocalContainer] javax.jcr.NoSuchWorkspaceException: dms
[INFO] [talledLocalContainer] at info.magnolia.repository.DefaultRepositoryManager.getSystemSession(DefaultRepositoryManager.java:236)


Generated at Mon Feb 12 04:56:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.