[FOLIO-2421] Interface mismatch between mod-orders-storage/mod-orders caused folio-testing build failure Created: 13/Jan/20  Updated: 03/Jun/20  Resolved: 13/Jan/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Ian Hardy Assignee: John Malconian
Resolution: Done Votes: 0
Labels: devops, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: Core: Platform

 Description   

Hi There, looks like there's an interface dependency mismatch between mod-orders-storage and mod-orders:

"Incompatible version for module mod-orders-9.1.0-SNAPSHOT.242 interface orders-storage.pieces. Need 3.2. Have 4.0/mod-orders-storage-10.0.0-SNAPSHOT.153"

That interface was recently moved from 4.0 to 3.2 in both modules.
https://github.com/folio-org/mod-orders/pull/243/files
https://github.com/folio-org/mod-orders-storage/pull/168/files

In mod-orders-storage, the version was downgraded from 10.0.0-SNAPSHOT to 9.1.0-SNAPSHOT.

Even though the interfaces agree at 3.2 on the tip of master, folio-testing will still fail. This is because folio-testing just uses the latest snapshot according to semvar (which would be the older 10.0.0-SNAPSHOT. with the 4.0 interface).

The snapshot builds pass because they use okapi for interface resolution.

To resolve this, I'd think the version number would have to be set back to 10.0.0, not sure why things went backwards here.



 Comments   
Comment by Ian Hardy [ 13/Jan/20 ]

Hi Aliaksandr Pautau Kruthi Vuppala. I see the version number went backwards here which I believe is causing the issue described above on folio-testing. Any reason not to just move it back ahead to resolve this?

Comment by John Malconian [ 13/Jan/20 ]

Increment version on master to 10.0.0-SNAPSHOT in POM. folio-testing build succeeded.

Generated at Thu Feb 08 23:20:31 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.