[MAGNOLIA-6285] Few harmless exceptions when migrating vanilla 5.3.9 to 5.4 Created: 07/Jul/15 Updated: 07/Jul/15 Resolved: 07/Jul/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | 54qa | ||
| 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 |
|
If someone uses a plain 5.3.9 bundle (i.e. not his own webapp) and replaces WEB-INF/libs with those from a plain 5.4 bundle, we get a few ClassNotFoundExceptions. Although they will be harmless if one doesn't use STK. info.magnolia.module.templatingkit.dam.STKAssetRenderer info.magnolia.module.templatingkit.imaging.generation.STKImageGenerator info.magnolia.module.devicedetection.filter.DeviceDetectionFilter info.magnolia.module.devicedetection.DeviceChannelResolver Obviously, STK is not bundled anymore, and a few other modules may not come transitively anymore (e.g. device-detection). That said, I'm not sure we do anything about it—at least filing it for reference, who knows... |
| Comments |
| Comment by Mikaël Geljić [ 07/Jul/15 ] |
|
On a side-note, in this "manual upgrade" scenario, one may also want to adjust log4j.xml, to prevent the harmless exceptions from the Reflections library: <!-- Reflections library spoils logs with harmless warnings; tries to look into native libs but none of its DefaultUrlTypes can handle them. --> <category name="org.reflections"> <priority value="ERROR" /> </category> This was introduced as part of |
| Comment by Mikaël Geljić [ 07/Jul/15 ] |
|
Indeed, now just closing it as "Not an issue", keeping it for reference. |