[MGNLTOOLS-21] versions removal is not performed on all workspaces Created: 05/Aug/08  Updated: 10/Jan/14  Resolved: 05/Aug/08

Status: Closed
Project: Repository Tools
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.0.2

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

Issue Links:
dependency
is depended upon by MGNLDATA-43 Magnolia 3.6.1, Update Issue - Activa... 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   

Currently running update35to36 script updates versions only for workspaces listed in default repositories.xml so all custom workspaces (for example data, dms, workflow) are not updated.



 Comments   
Comment by Jan Haderka [ 05/Aug/08 ]

Further more update of data workspace fails due to missing MetaData on dataFolder type. This is caused by the sequence in which update happens. Current order of events:

  1. update node types definition and add MetaData as mandatory child for dataFolder type (mgnltools)
  2. remove versions fails due to missing MetaData (mgnltools)
  3. add missing MetaData (DataModule update task)

Possible fixes:

  • add missing MetaData as a part of versions removal (would still need to be executed again in the data module update task at least for CE) or
  • add MetaData as mandatory child for dataFolder only after version cleanup.
Comment by Jan Haderka [ 05/Aug/08 ]

r17202

Generated at Mon Feb 12 10:40:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.