[MGNLRES-296] New light module created with CLI on Windows machine is not immediately registered. Created: 23/Jan/17  Updated: 29/Mar/22  Resolved: 02/Feb/17

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: 2.5.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Tomáš Gregovský Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 10


Issue Links:
duplicate
duplicates MAGNOLIA-6945 light modules added during runtime no... 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:
Team: Nucleus

 Description   

Last week during a POC two external developers used Windows 10 machines. Both of them installed Magnolia EE 5.5.1 (tomcat bundle) and have it running. Then they used CLI to create light module and to create a page. In this phase usually in Macbook, you can go to pages and have that page template immediately available, same as new light module show up in Resources app. But for both guys it doesn't show up, when both of them restarted Magnolia instance all was fine and working. Next template creation works fine.

I remember similar issue during another POC 3 months ago on another Windows machines.

It's not a big deal to restart, it's just a weird behaviour especially if we are saying you can develop on running instance without restarting.



 Comments   
Comment by Jan Haderka [ 23/Jan/17 ]

I guess that is not CLI specific, but true for any first light module created on Windows. Can anyone verify this assumption?

Comment by Tomáš Gregovský [ 23/Jan/17 ]

Sure, it's probably not CLI specific, but CLI does crate bunch of folders and files in same time and that may be relevant, so I just wanted to mention it... but maybe manually created lite module on windows will cause same issue... don't know

Comment by Jan Haderka [ 24/Jan/17 ]

Do you remember if the location specified in magnolia.resources.dir existed when tomcat was started or was created only once Magnolia was running?

Comment by Michael Mühlebach [ 02/Feb/17 ]

Closed it because sounds like the exact same issue as MAGNOLIA-6945. (and czimmermanns issue has a nice part on how to reproduce it )

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