OpenMRS Platform 2.3.0-beta released for testing

@ruhanga , a momment before that , from this talk thread here

we are coming to a resolution of reverting this commit here

see talk discussion that led to that commit here

, So it may need reverting and also some testing

but please first follow the discusion above for more insight

I agree with thisā€¦ annotations are certainly the more ā€œmodernā€ way for doing things so we should seriously consider upgrading, but we should do it at a point when we are confident to have the resources for a details regression test, and a strategy for avoiding things like the ā€œunused_tablesā€.

Take care, Mark

1 Like

Thanks @mozzy for timely pointing this out,

Iā€™ve gone through the thread you shared but unfortunately Iā€™m running out of bandwidth. I hope to get all this tested after reverting locally before merging this though.

1 Like

What were the other issues? I thought we addressed them

@wyclif, the above revert issue is annotations unrelated.

@mozzy, Iā€™ve been doing a couple of tests, and reverting this is effective when using the SDK. By this I mean, installing a fresh instance of the platform with the current version of the SDK adds the admin user name to the admin systemID as was fixed. However this is not the case when running on an enterprise tomcat server. I would think the later is not a big issue.

1 Like

Have you done the tests, after reverting the commit ?

Yes @mozzy. :slight_smile:

1 Like

sure thats the expected behaviour.

thats only possible when running with the latest SDK , Docker or the standalone , if am not mistaken. So i think ideally thats the expected behaviour
cc @dkayiwa

1 Like