You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have support in mybatis for jdk 16+. Due to this and consideration each maintainer my be using different jdks at same time, we run risks of releasing mixed release content by mistake as was such the case with 3.5.13. By luck that was not occurring before but likelihood is very high now. We should review our current logic and restructure into a multi jar release. That does mean we should further drop lower jdk build support which is fine. If we need to, we could go as far as having simple GH-Actions showing usage at jdk 8 and above. Or maybe even explore new dev contains github offers to ensure we are not losing anything. Should be safe though, we already dropped jdk 8 from builds.
The text was updated successfully, but these errors were encountered:
I'll take a look into what needs to occur here, I've seen this in many projects now such as java metro so it shouldn't be that difficult to setup. At the moment, at least from mybatis downstream modules, none seem to have any issues with how 3.5.13 was released and there may not really be. Will monitor the issue regardless and this ticket can further serve as notice to users searching in case of issues encountered in currently release.
We have support in mybatis for jdk 16+. Due to this and consideration each maintainer my be using different jdks at same time, we run risks of releasing mixed release content by mistake as was such the case with 3.5.13. By luck that was not occurring before but likelihood is very high now. We should review our current logic and restructure into a multi jar release. That does mean we should further drop lower jdk build support which is fine. If we need to, we could go as far as having simple GH-Actions showing usage at jdk 8 and above. Or maybe even explore new dev contains github offers to ensure we are not losing anything. Should be safe though, we already dropped jdk 8 from builds.
The text was updated successfully, but these errors were encountered: