[MAGNOLIA-2859] ModuleVersionHandler testability Created: 01/Sep/09 Updated: 09/Jun/15 Resolved: 03/Sep/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3, 4.1.1 |
| Type: | Improvement | Priority: | Major |
| 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 |
|
Some improvements have already been committed, some more are coming up
|
| Comments |
| Comment by Magnolia International [ 02/Sep/09 ] |
|
Refactoring the web.xml related conditions could help testability too - at the moment, using WebXmlConditionsUtil usually implies those conditions to be executed immediately and not when ModuleManager.performInstallOrUpdate() is called. |