[MAGNOLIA-2348] Review usage of ModuleLoader Created: 02/Sep/08 Updated: 03/Feb/09 Resolved: 20/Jan/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.5, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.5.5, 3.5.6, 3.5.7, 3.5.8, 3.6, 3.6.1 |
| Fix Version/s: | 4.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Magnolia International |
| Resolution: | Obsolete | 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Deprecated ModuleLoader does not see modules using new module life cycle. Make sure that wherever it is still used to obtain module instances ModuleRegistry is queried as well. |
| Comments |
| Comment by Jan Haderka [ 02/Sep/08 ] |
|
Same goes for deprecated ModuleRegistration class as well. |
| Comment by Magnolia International [ 20/Jan/09 ] |
|
ModuleLoader and ModuleRegistration have been removed with |