Recently we got some new changes in the qa-server where @dkayiwa added some changes here in order to unblock the qa team. so my question is, did those changes get incorporated into any of the refapp2 versions in the sdk? I ask because when i trigger tests to run against my previous local instance and demo server all tests fail but against the qaserver they pass. So i opted to create a new server locally with those changes in the qaserver.
However when i visit JFrog ( im guessing those should be the snapshots of 2.13.0 which should contain those changes–correct me if am wrong) and it should be among the options when i try to create a new server.
Those changes added are not yet incoperated in any of our reference applications. FYI all changes incorporated in reference applications must be first be released using our CIs which is bamboo unless it’s on platform core. those were the fix to enable our server pass depending on the core version.
Are you still having issues with runing your tests locally ?
This might be totally irrelevant to the heart of the question here, but: I was under the impression that we are only using Sourceforge now, and no longer jfrog (esp since I thought jfrog was going to be end-of-lifed soon). (@dkayiwa do I have this wrong?)
dunno if the problem is on my end but i land into this blocker with the pointer being Plugin org.openmrs.maven.plugins:openmrs-sdk-maven-plugin:4.4.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.openmrs.maven.plugins:openmrs-sdk-maven-plugin:jar:4.4.0-SNAPSHOT.
JFrog (the company) provided us with two services Bintray (which is completely gone by now) and Artifactory (which is still actively supported and is our Maven repository). All of our Java code is ultimately hosted on Artifactory (which is at the URL openmrs.jfrog.io).
We probably should delete the 3.0.0-SNAPSHOT version from there though and rename the corresponding artifact. What we bundle under that name for 3.0.0 is currently incompatible with the SDK.