[MAGNOLIA-6289] Light modules created as symlinks are not monitored for changes Created: 08/Jul/15 Updated: 31/Jan/17 Resolved: 31/Jan/17 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | configuration |
| Affects Version/s: | 5.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Jozef Chocholacek | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | configuration, symlink, tomcat | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux (Fedora 22), Tomcat 7.0.63 |
||
| Issue Links: |
|
||||||||
| 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: | |||||||||
| Description |
|
When a light module is created as a symbolic link (e.g. to a subfolder of a cloned git repository), its content is not monitored for changes/new files. This can be a typical use case for both development and deployment, so I consider this bug quite serious. |
| Comments |
| Comment by Christopher Zimmermann [ 08/Jul/15 ] |
|
Note that there is a property in magnolia.properties file "magnolia.resources.dir" where you can specify a directory to be scanned. |
| Comment by Jozef Chocholacek [ 08/Jul/15 ] |
|
Yes, that could be a possible workaround. We'll have to adjust our repository structure then, and have the light modules in a separate folder, instead together with the standard modules (and theme(s) and webapp) in a maven project's folder. They wouldn't (usually) be Maven projects, anyway. |
| Comment by Christopher Zimmermann [ 31/Jan/17 ] |
|
Duplicates |