SimpleScheduler - fix CronTrigger#evaluate()

[mkouba]

• resolves Scheduler is not triggered or triggered 2 times randomly with native image #17724

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building ab144e2

Status	Name	Step	Test failures	Logs	Raw logs
✖	Initial JDK 11 Build	Set up JDK 11	⚠️ Check →	Logs	Raw logs

[machi1990]

LGTM. CI was not happy with the first run though, I relaunched it.

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building ab144e2

Status	Name	Step	Test failures	Logs	Raw logs
✖	Initial JDK 11 Build	Set up JDK 11	⚠️ Check →	Logs	Raw logs

[mkouba]

LGTM. CI was not happy with the first run though, I relaunched it.

GitHub has problems: https://www.githubstatus.com/ :-(

[mkouba]

The change is described in #17724 (comment)

[gsmet]

@mkouba VERY bad idea to rename the logger in the same commit. I have conflicts... When you want to backport a fix, please do NOT make cosmetic changes that don't bring anything to the plate.

[gsmet]

I fixed the conflicts myself by saying that for next time.

[mkouba]

@mkouba VERY bad idea to rename the logger in the same commit. I have conflicts... When you want to backport a fix, please do NOT make cosmetic changes that don't bring anything to the plate.

@gsmet I'm really sorry about that. I tried to make a diff locally and saw no conflicts. But this change was not only about renaming the logger, I also added/removed some log messages. Was it really the rename itself that caused the conflict?

[gsmet]

Yes. Some methods are not in 1.13 and the fact that the logger name had changed made them present in the diff as they are logging something. There's a good chance they would have been ignored otherwise.

It wasn't too hard to fix it but for a more complex patch, that could have been a major pain thus my message.