[FOLIO-1755] verify dependency resolution checking Created: 30/Jan/19 Updated: 03/Jun/20 Resolved: 06/Feb/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Adam Dickmeiss | Assignee: | Ian Hardy |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, core, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Sprint: | Core: Platform - Sprint 56 | ||||||||||||||||||||||||||||||||
| Story Points: | 0.5 | ||||||||||||||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||||||||||||||
| Description |
|
Problem When posting a new release of mod-kb-ebsco-java to the registry where only releases of modules are considered in the dependency check. This gives numerous errors. See attached post.txt. Interface problems:
The problem is related to the bug in Okapi: Okapi-697. Task When Okapi-697 is resolved update the local installation of FOLIO to the Okapi version that includes the fix, pull the MD from folio-registry and perform an upload of mod-kb-ebsco-java ModuleDescriptor to verify that the dependency problem is gone. |
| Comments |
| Comment by Adam Dickmeiss [ 30/Jan/19 ] |
|
I think we should lax the dependency and only consider dependencies on immediate require list of the module being posted.
|
| Comment by Adam Dickmeiss [ 04/Feb/19 ] |
|
Did you have a chance to look into this? |
| Comment by John Malconian [ 04/Feb/19 ] |
|
Adam Dickmeiss Still on my TODO. |
| Comment by Ian Hardy [ 06/Feb/19 ] |
|
Verified dependency checking. Using a local instance of Okapi 2.41, pulled module descriptors from the folio registry. posted mod-kb-ebsco to local Okapi with preRelease=false w/o dependency errors. Also tried setting un-meetable requirements in a few MDs files to trigger a dependency error when preRelease is set to false. folio_users-2.20.0 will still fail if preRelease is false since login 4.7 is not provided by a released module as noted above. |