[MAGNOLIA-5171] ModuleDescriptionReader could be more helpful when a resource isn't found Created: 09/Jul/13 Updated: 26/Jul/13 Resolved: 09/Jul/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | testing |
| Affects Version/s: | None |
| Fix Version/s: | 4.5.10, 5.0.2, 5.1 |
| Type: | Improvement | Priority: | Trivial |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| 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 |
|
In tests, we do things like BetwixtModuleDefinitionReader.readFromResource(path); when that path is wrong (or, more typically, the expected file/dependency isn't on the classpath), we just get a lame NullPointerException. An exception with the path would help. |
| Comments |
| Comment by Magnolia International [ 09/Jul/13 ] |
|
done on master and cherry-picked on 4.5.x branch |