From 0570e6e2180137a23a0aab7d37edc0a1528e27cc Mon Sep 17 00:00:00 2001 From: vramik Date: Wed, 30 Aug 2017 11:55:52 +0200 Subject: [PATCH] KEYCLOAK-5354 update READMEs (#4443) --- README.md | 2 +- misc/UpdatingDatabaseSchema.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index abb0bc253c..3fafffc670 100755 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ Starting Keycloak To start Keycloak during development first build as specified above, then run: - mvn -f testsuite/integration-deprecated/pom.xml exec:java -Pkeycloak-server + mvn -f testsuite/utils/pom.xml exec:java -Pkeycloak-server To start Keycloak from the server distribution first build the distribution it as specified above, then run: diff --git a/misc/UpdatingDatabaseSchema.md b/misc/UpdatingDatabaseSchema.md index d9dc9c2bdb..cb4a0f8bf4 100644 --- a/misc/UpdatingDatabaseSchema.md +++ b/misc/UpdatingDatabaseSchema.md @@ -35,7 +35,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-deprecated/pom.xml exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-update'` + `mvn -f testsuite/utils/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` @@ -50,11 +50,11 @@ add entries to the `change-set` to update existing data if required. When you have update the change-set Hibernate can validate the schema for you. First run: rm -rf keycloak*h2.db - mvn -f testsuite/integration-deprecated exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='update' + mvn -f testsuite/utils/pom.xml exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='update' Once the server has started fully, stop it and run: - mvn -f testsuite/integration-deprecated exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-validate' + mvn -f testsuite/utils/pom.xml exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-validate' Testing database migration