libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

Broken link in documentation

Browse source 
Closes #29233

Signed-off-by: Douglas Palmer <dpalmer@redhat.com>
This commit is contained in:
Douglas Palmer 2024-05-02 11:04:02 -07:00 committed by Pedro Igor
parent 8a0322cc13
commit 26eaa4f83f
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/documentation/server_development/topics/extensions.adoc
View file

@ -137,7 +137,7 @@ EntityManager em = session.getProvider(JpaConnectionProvider.class).getEntityMan
Company myCompany = em.find(Company.class, "123"); Company myCompany = em.find(Company.class, "123");
---- ----
The methods `getChangelogLocation` and `getFactoryId` are important to support automatic updating of your entities by Liquibase. https://www.liquibase.com/community[Liquibase] The methods `getChangelogLocation` and `getFactoryId` are important to support automatic updating of your entities by Liquibase. https://www.liquibase.com/community/contributors[Liquibase]
is a framework for updating the database schema, which {project_name} internally uses to create the DB schema and update the DB schema among versions. You may need to use is a framework for updating the database schema, which {project_name} internally uses to create the DB schema and update the DB schema among versions. You may need to use
it as well and create a changelog for your entities. Note that versioning of your own Liquibase changelog is independent it as well and create a changelog for your entities. Note that versioning of your own Liquibase changelog is independent
of {project_name} versions. In other words, when you update to a new {project_name} version, you are not forced to update your of {project_name} versions. In other words, when you update to a new {project_name} version, you are not forced to update your