[MAGNOLIA-6837] When path to yaml file changed windows not observing that file anymore Created: 24/Oct/16  Updated: 29/May/17  Resolved: 22/May/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.8
Fix Version/s: 5.5.3

Type: Bug Priority: Major
Reporter: Tomáš Gregovský Assignee: Ilgun Ilgun
Resolution: Obsolete Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6897 DirectoryWatcher on Windows requires ... 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
Date of First Response:
Sprint: Basel 97
Story Points: 1

 Description   

During a training last week we have discovered a bug on windows 7 devices (3 attendees had win7, all had same issue)...

For light development when you want to overwrite file from filesystem, for example /<light-modules>/mtk/template/components/textImage.yaml, so when you create this path and also file then you figure out a typo in path ('template' instead of 'template*s*'), so will rename that folder to right name but then Magnolia stops observe this file until you restart it... last message in log is still with registered definition for wrong path and even with edits in file itself or changing path again, nothing will trigger observing of that definition again.

Just restart helps.



 Comments   
Comment by Christopher Zimmermann [ 01/Nov/16 ]

Version was 5.4.8 or 5.4.9

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