[MAGNOLIA-6338] New template scripts on the classpath are not loaded Created: 12/Aug/15 Updated: 03/Oct/17 Resolved: 01/Feb/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | resource-loader |
| Affects Version/s: | 5.4 |
| Fix Version/s: | 5.4.4, 5.4.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Christian Ringele | Assignee: | Ilgun Ilgun |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | 0d | Remaining Estimate: | 0d |
| Σ Time Spent: | 7h | Time Spent: | 7h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||||||||||||||
| Epic Link: | Resource reloading without restart | ||||||||||||||||||||||||||||||||||||
| Sprint: | Basel 24, Basel 31 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||||||||||||||||||
| Description |
| Comments |
| Comment by Christian Ringele [ 13/Aug/15 ] |
|
Work around:
# The directory to expose file system resources from
magnolia.resources.dir=${magnolia.home}
to the directory within you checked out char module to: /src/main/resources (Or a soft link in Linux to /src/main/resources, and then point to the soft link with the property) |
| Comment by Mikaël Geljić [ 13/Aug/15 ] |
|
To shed some details: ClasspathResourceOrigin internally uses the Reflections library, does an initial scan upon startup. Now because we cache the tree structure of classpath resources, we never detect new files which are not YAML. And indeed, using the file-system resource origin is a valid workaround. Except I'd rather make this explicit by keeping this directory around the webapp, rather than hard-pointing the magnolia.resources.dir property to one specific module (it would already be a dead end if you want to work on multiple modules at the same time). |
| Comment by Aleksandr Pchelintcev [ 02/Dec/15 ] |
|
commented the PR |
| Comment by Federico Grilli [ 24/Dec/15 ] |
|
QA was done as follows
TEST classpath scanning on
TEST classpath scanning on and no observation of FTLs
TEST classpath scanning off
|
| Comment by Michael Mühlebach [ 01/Feb/16 ] |
|
This issue should be solved by |