Fix IBM classloader regression #1301
Merged
Conversation
Migration to Location from String in ClassPathResolver on cbc9fef introduced regression in websphere classloader, location there resolves to "classpath:db/migration/flyway.location" which causes IBM classloader to miss resources, added getPath() like in normal classloader flow, tested on WebSphere 8.5.5.9 jdk8.
|
Thanks! Merged. |
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.
Migration during #979 fix introduced regression on #175
Migration to Location from String in ClassPathResolver on cbc9fef introduced regression in websphere hack from #175 in ClassPathScanner. Location there resolves to "classpath:db/migration/flyway.location" which renders resource not visible for IBM classloader. Added getPath() like in normal classloader flow. Tested on WebSphere 8.5.5.9 jdk8.