[MAGNOLIA-6944] When a symbolic link is added to resources dir, all existing contents should be loaded Created: 31/Jan/17  Updated: 26/Feb/18  Resolved: 23/Feb/18

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.5.1
Fix Version/s: 5.6.3

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Federico Grilli
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-7260 Backport - When a symbolic link is ad... Closed
relation
is related to MAGNOLIA-6846 Resource directories registered via s... 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
Release notes required:
Yes
Date of First Response:
Sprint: Basel 133, Basel 134, Basel 135
Story Points: 5

 Description   

When a symbolic link is added to a running magnolia instance, the existing contents of the linked directory are not loaded by magnolia.

The existing contents should be loaded - similar to if I add a normal directory of files.

Note:
Currently if an existing file is touched in a linked directory, Magnolia does detect and load the file. And any new files added to the linked directory are also handled properly.



 Comments   
Comment by Christopher Zimmermann [ 17/Jan/18 ]

Using symbolic links is supported for light modules and is a best practice. It is useful in development to have multiple projects linking to the same shared module. It can be useful in production for more flexibllity in the setup of the filesystem.
This bug gets in developers ways and simply reduces trust in the whole light development loading system. Developers who encounter it dont know why the system is not working as advertised and need to resort to restarting the server, which light development promises is not necessary.

I don't know how widespread usage of symlinks is, but I imagine fairly common. Its just a natural solution a developer is going to come up with during projects.

Comment by Christopher Zimmermann [ 08/Feb/18 ]

Verified: Problem still exists on 5.6.
(Things show up in the resources app - but not in the definitions app.)

Comment by Federico Grilli [ 13/Feb/18 ]

In spite of successful pre-integration QA and local testing by several devs both on mac and linux, integration failed twice in a row on Jenkins. Once due to concurrent modification exception, second one simply did not meet the expected condition. Reopening and removing from 5.6.2 changelog

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