Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CronTrigger uses new Date() instead of context's Clock #27546

Closed
markuspfeiffer opened this issue Oct 11, 2021 · 0 comments
Closed

CronTrigger uses new Date() instead of context's Clock #27546

markuspfeiffer opened this issue Oct 11, 2021 · 0 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Milestone

Comments

@markuspfeiffer
Copy link

The nextExecutionTime(TriggerContext) method of CronTrigger uses new Date(); instead of using the specified context's clock. This makes it unnecessarily hard to unit test classes that create a trigger internally.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Oct 11, 2021
@jhoeller jhoeller self-assigned this Oct 11, 2021
@jhoeller jhoeller added in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Oct 11, 2021
@jhoeller jhoeller added this to the 5.3.11 milestone Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Projects
None yet
Development

No branches or pull requests

3 participants