Fix for @DatabaseSetup annotation on superclasses #138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
February 15, 2017 20:21
|
This fix has been done in a maintained repository: https://github.com/ppodgorsek/spring-test-dbunit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
This pull request should fix issue #103. The class
DbUnitRunnerwill now use the overloadedfindAnnotationmethod on theorg.springframework.core.annotation.AnnotationUtilsclass in Spring Core that takes aClass<?>as an argument opposed toAnnotatedElement.The latter will only look for the annotation on the given class while the other methods tries to look on it's parent classes/interfaces if the annotation is not present on the given class itself.This reintroduces the behaviour from older version of spring-test-dbunit.