Warnings when running with Quarkus 3.28.3

[sgift]

I've created a blank project via quarkus cli (as suggested in the readme) and get these warnings when starting it in dev mode. Is this a problem?

[metacosm]

Hi, this isn't normally an issue and we should probably document it better but the idea here is that some version mismatches between dependencies might possibly cause issues so we warn of them when detected. This should only serve as information if people do experience weird issues that they can't explain otherwise.

[philippart-s]

But, it's strange that appends with a fresh and blank project created with the Quarkus CLI?
All dependencies should be ok in this case? No?

[metacosm]

But, it's strange that appends with a fresh and blank project created with the Quarkus CLI? All dependencies should be ok in this case? No?

QOSDK checks the alignment of 3 libraries: JOSDK, Fabric8 client and Quarkus, or more specifically, the alignment of the Fabric8 client versions which JOSDK uses and the version that Quarkus provides. This is the main problem point: it had happened in the past that attempting to use QOSDK with differing versions of the client between JOSDK and Quarkus caused issues. In the case above, you can see that there is a discrepancy between the version that JOSDK was compiled against (7.3.1) and the version that is provided by Quarkus (7.4.0) and the version with which QOSDK was built (7.2.0). This usually isn't a problem but we've had issues (usually when using native compilation) in the past in these situations so we decided to implement a version alignment check to help diagnose issues.

More specifically, regarding your question, this should indeed not happen with a fresh project if we released a new QOSDK version for every Quarkus version (which we don't do). We usually try to release a new version of JOSDK with each new version of the Fabric8 client, then update Quarkus with that version, then update QOSDK accordingly but it might happen that there is a timelapse before that actually happens, in which case the warnings will show up.

To be fair, these alignment issues were more of a problem when the project was still new: we haven't observed any such issues recently so maybe it might make sense to remove these warnings now and make the version alignment check an optional build step instead, to be used only as a diagnostic tool when encountering unexplained issues.

[philippart-s]

Thank you @metacosm your explanation is very transparent and clear 😊