From 28cc45a3fb70670585f901ae82910f0c6cf43583 Mon Sep 17 00:00:00 2001 From: Gerrit Meier Date: Fri, 20 Jan 2023 12:41:34 +0100 Subject: [PATCH] GH-2656 - Fix broken link in reference documentation. Linked repository got renamed. Closes #2656 --- src/main/asciidoc/appendix/migrating.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/asciidoc/appendix/migrating.adoc b/src/main/asciidoc/appendix/migrating.adoc index 51686180a..ff9bb3d9b 100644 --- a/src/main/asciidoc/appendix/migrating.adoc +++ b/src/main/asciidoc/appendix/migrating.adoc @@ -23,7 +23,7 @@ As there is always a Spring Data version corresponding to Neo4j-OGM, you would h Spring Data however depends on Spring Framework and then the arguments from the first bullet apply. Being unsure about which building blocks to include:: It's not easy to get the terms right. -We wrote the building blocks of an SDN+OGM setting https://michael-simons.github.io/neo4j-sdn-ogm-tips/what_are_the_building_blocks_of_sdn_and_ogm.html[here]. +We wrote the building blocks of an SDN+OGM setting https://michael-simons.github.io/neo4j-examples-and-tips/what_are_the_building_blocks_of_sdn_and_ogm.html[here]. It may be so that all of them have been added by coincidence and you're dealing with a lot of conflicting dependencies. TIP: Backed by those observations, we recommend to make sure you're using only the Bolt or http transport in your current application before switching from SDN+OGM to SDN.