#Warning from compiling a persist module
1 messages · Page 1 of 1 (latest)
FYI:
Ballerina 2201.8.6 (Swan Lake Update 8)
Language specification 2023R1
Update Tool 1.4.2```
Hi @shrewd lichen
We will check on this and get back to you. @verbal fossil FYA.
@shrewd lichen The warning arises because we've recently released a patch for the persist module, yet persist.inmemory remains in the previous version. This leads to a warning because the system selects the latest version when encountering conflicting versions, potentially resulting in inconsistencies. In this instance, our changes do not impact the behavior.
I think we got this warning sometime back for a different release. Is there a way to avoid this happening again?
@open ice The main reasons are, we are locking persist native dependencies in Ballerina.toml file due to dependently type function limitation and dependencies should available in maven central. As we are going to resolve native dependencies from WSO2 nexus from update 09, we can avoid this issue to some extent. but still, when we do a patch release after the release, we need to ask user to update the dependency version in toml file to avoid this warning.
If we can support the dependent type function to be written in Ballerina or release the persist tool independently, we can avoid it completely.
@verbal fossil We can avoid this by specifying the groupId, artifactId, and the version for the platform dependencies. For ballerina and ballerinax libraries, if two platform libraries with the same groupId and the artifactId are detected, we pick the latest without issuing a warning.
We are specifying it as below in the Ballerina.toml file. but still we are getting the warning. [[platform.java17.dependency]] groupId = "io.ballerina.stdlib" artifactId = "persist.inmemory-native" version = "1.2.0"