[MAGNOLIA-2300] ModuleManagerImpl.checkForUpdateOrInstall breaks its stated contract Created: 05/Aug/08 Updated: 19/Dec/16 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, updatemechanism |
| Affects Version/s: | 3.6.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Jan Haderka | Assignee: | Magnolia International |
| Resolution: | Won't Do | 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)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Javadoc for ModuleManager.checkForInstallOrUpdates() states the method implementation is supposed to check for existence of install or update tasks that needs to be executed. However implementation of the method in ModuleManagerImpl also loads repositories when there are not install/update tasks to execute. |
| Comments |
| Comment by Magnolia International [ 20/Jan/09 ] |
|
The javadoc has been fixed a while ago. Bumping this to 4.1, we might want to have all workspaces handled by modules (register them through module's module descriptor), so this part of the MM code could be improved/cleaned. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |