[MAGNOLIA-2525] Miserable failure on attempt to start Magnolia with a module which uses the info.magnolia.cms.module api Created: 22/Dec/08 Updated: 23/Jan/13 Resolved: 23/Jan/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.0 |
| Fix Version/s: | 4.0 |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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 |
|
Since this was removed ( We should at least be able to ignore/skip such modules and let Magnolia start without them. |
| Comments |
| Comment by Magnolia International [ 22/Dec/08 ] |
|
This was actually fixed by r20831. |
| Comment by Magnolia International [ 22/Dec/08 ] |
|
The previous commits fixed issues when the module class or their dependencies were importing RegisterException. There is another issue if the module class itself extends the remove Module classes, ie java.lang.NoClassDefFoundError: info/magnolia/module/admininterface/AbstractAdminModule |
| Comment by Magnolia International [ 23/Jan/09 ] |
|
Now logs and skips when the module class can't be instanciated |