Allow customization for db migration #1061
Merged
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.
Moved
fi.nls.oskari.servlet.WebappHelper
to new pathorg.oskari.init.OskariInitializer
. This file is usually not customized so the change shouldn't have any effect on most instances. However we do have an instance that had WebappHelper copied to the application codebase with minor change to run migrations a bit different than in the built-in one. Mainly using other db-credentials for migrations than the app usually uses at runtime.This adds a way of doing just that without the need to copy the whole file and maintain after changes. With this the application can add a custom class that implements
org.oskari.init.CustomMigration
and define oskari-ext.properties with:On launch the application would then run
foo.bar.CustomMigrationImpl.migrateDB()
instead of the normal migration process.