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

move junit explicitly to the test scope #82

Merged
merged 1 commit into from
Jan 14, 2020

Conversation

ystarikovich
Copy link

No description provided.

@kagkarlsson
Copy link
Owner

Oh, good catch. Missed this one. Thanks 👍

@kagkarlsson kagkarlsson merged commit 1949601 into kagkarlsson:master Jan 14, 2020
@kagkarlsson
Copy link
Owner

Do you need a new release with this asap?

@ystarikovich
Copy link
Author

Not super urgent right now. I'm also thinking to submit more generic Customizer which we used in our auto configuration on behalf of @poberbichler. What do you think about this enhancement, then Scheduler bean creation should be simplified.


import com.github.kagkarlsson.scheduler.SchedulerBuilder;

/**
 * Callback interface that can be used to customize a {@link SchedulerBuilder}
 */
@FunctionalInterface
public interface DbSchedulerCustomizer {
    void customize(SchedulerBuilder schedulerBuilder);
}

@kagkarlsson
Copy link
Owner

It was actually released yesterday since I had another fix I needed released.

Will have a look at your suggestion for spring boot

@kagkarlsson
Copy link
Owner

Your suggestion for DbSchedulerCustomizer makes sense. There might be a source of confusion since you will be able to override properties from DbSchedulerProperties, but if it is mentioned explicitly in the javadoc that should be fine.

Customizer apply probably should be moved to the end of DbSchedulerAutoConfiguration.schedule(..) method, so that anything you set in the customizer will have precedence.

@kagkarlsson
Copy link
Owner

Feel free to submit a PR :)

evenh pushed a commit to evenh/db-scheduler that referenced this pull request Oct 1, 2020
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