Skip to content

Conversation

@hazendaz
Copy link
Member

few modernization issues detected with parent 37 snapshot.

@hazendaz hazendaz self-assigned this Dec 10, 2022
@hazendaz
Copy link
Member Author

ok seems a bug in the modernizer, will remove the one and try the other.

@hazendaz hazendaz force-pushed the master branch 2 times, most recently from b6b09d5 to 67cb10d Compare December 10, 2022 16:52
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.009%) to 87.313% when pulling 67cb10d on hazendaz:master into 9ea182f on mybatis:master.

@hazendaz
Copy link
Member Author

This one works as tests are set to 11. possibly this is causing a bug in modernizer as it fails now at 37 if we don't update the source side which we cannot yet. For now, taking what we can from that and will continue to review that before parent is released.

@hazendaz hazendaz merged commit ad002e8 into mybatis:master Dec 10, 2022
@hazendaz
Copy link
Member Author

no bug in modernizer, issue is due to mybatis becoming jdk 16 when ran with defaults and proper jdk involved. In that scenario it will want to fix the code which I now recall. Same was true with what I patched here but after last parent we now allow jdk 11 with tests so that one is now ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants