[MGNLIMG-128] Verify whether module descriptor dependency on activation is necessary Created: 02/Apr/14 Updated: 02/Oct/23 Resolved: 02/Oct/23 |
|
| Status: | Closed |
| Project: | Imaging |
| Component/s: | None |
| Affects Version/s: | 3.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Greg writes:
|
| Comments |
| Comment by Mikaël Geljić [ 13/Mar/17 ] |
|
Dep is there only because any module declaring a workspace "requires" activation. SetupModuleRepositoriesTask (via default MVH) fails to get an ActivationManager instance, then blows with NPE.
Meanwhile, I see no reason either, why not removing the dep from module descriptor, even straight away. Either way, without my patch Magnolia won't start or install properly. |
| Comment by Laura Delnevo [ 02/Oct/23 ] |
|
Hello,
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. |