From 371c798116cf6dd9358535ce563ed1cb3a7e5228 Mon Sep 17 00:00:00 2001 From: Giriraj Sharma Date: Mon, 11 May 2015 18:38:02 +0530 Subject: [PATCH] Minor issue: Fixed non-resolvabe pom error while updating schema via hibernate. --- misc/UpdatingDatabaseSchema.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/misc/UpdatingDatabaseSchema.md b/misc/UpdatingDatabaseSchema.md index 274669c6a6..375d909c1f 100644 --- a/misc/UpdatingDatabaseSchema.md +++ b/misc/UpdatingDatabaseSchema.md @@ -37,7 +37,7 @@ You can also have Liquibase and Hibernate create one for you. To do this follow 3. Make a copy of the database: `cp keycloak.h2.db keycloak-old.h2.db` 3. Run KeycloakServer to make Hibernate update the schema: - `mvn -f testsuite/integration exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-update'` + `mvn -f testsuite/integration/pom.xml exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-update'` 4. Wait until server is completely started, then stop it 5. View the difference: `mvn -f connections/jpa-liquibase/pom.xml liquibase:diff -Durl=jdbc:h2:keycloak-old -DreferenceUrl=jdbc:h2:keycloak` @@ -76,4 +76,4 @@ It should be added last to the `DefaultMongoUpdaterProvider#updates` array. Testing database migration -------------------------- -Get the database from an old version of Keycloak that includes the demo applications. Start the server with this and test it. \ No newline at end of file +Get the database from an old version of Keycloak that includes the demo applications. Start the server with this and test it.