[MAGNOLIA-3522] magnolia.properties entries are not trimmed Created: 20/Jan/11 Updated: 02/Feb/11 Resolved: 20/Jan/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.4.1 |
| Fix Version/s: | 4.4.2 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Ryszard Koźmik | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Description |
|
By mistake we've added following lines in our magnolia.properties since those needed modification while upgrading to 4.4.1: magnolia.cache.startdir=${magnolia.app.rootdir}/cache Theoretically those lines look ok but at the end they have a whitespace. It resulted in Magnolia creating such directories on next start and we ended up with 'repositories', 'repositories ', 'cache' and 'cache ' in our directory structure. This was probably a killer for our upgrade that happened just after this properties edition. So, it could be useful to trim such properties as those can potentially lead to data inconsistency between db and repositories for example. |