develop to master #175
Closed
develop to master #175
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added spring-maven dependency execution for fat-jar Added maven-version plugin Updated to version 1.1.1
Added spring-maven dependency execution for fat-jar Added maven-version plugin Updated to version 1.1.1
New version 1.1.2
New version 1.1.2
# Conflicts: # keycloak-storage-provider/pom.xml # pom.xml # sts-common/pom.xml # sts-example/pom.xml # sts-keymanagement/pom.xml # sts-keymanagement/sts-keymanagement-api/pom.xml # sts-keymanagement/sts-keymanagement-impl/pom.xml # sts-persistence-jpa/pom.xml # sts-persistence-mongo/pom.xml # sts-pop/pom.xml # sts-resource-server/pom.xml # sts-secret-server/pom.xml # sts-secret/pom.xml # sts-server-info/pom.xml # sts-service-component-example/pom.xml # sts-simple-encryption/pom.xml # sts-spring/pom.xml # sts-token-auth/pom.xml # sts-token/pom.xml
New version 1.1.2
New version 1.1.2 Added missing classifier
New version 1.1.3 Added missing classifier
…plementation because there is an error with the typeresolver due to old java 6 dependency
…due to miss configuration
…abases because of missing sequences in hibernate
* Increased version to 1.1.16 * Changed cors configuration to set disabled first to prevent cors configuration exceptions * Updated version to 1.17 * Replaced deprecated PostgreSQL94Dialect with PostgreSQLDialect * spring.jpa.open-in-view ist standardmäßig aktiviert: behoben * Excluded SecurityAutoConfiguration to prevent Spring from creating a default user * Changed SecurityConfiguration to allow access to swagger * Changed SecurityConfiguration to allow access to swagger * Excluded AutoConfiguration for UserDetailsService * Added RequestMatchers to address warnings for ignored paths * Increased version to 1.19
* Increased version to 1.1.16 * Changed cors configuration to set disabled first to prevent cors configuration exceptions * Updated version to 1.17 * Replaced deprecated PostgreSQL94Dialect with PostgreSQLDialect * spring.jpa.open-in-view ist standardmäßig aktiviert: behoben * Excluded SecurityAutoConfiguration to prevent Spring from creating a default user * Changed SecurityConfiguration to allow access to swagger * Changed SecurityConfiguration to allow access to swagger * Excluded AutoConfiguration for UserDetailsService * Added RequestMatchers to address warnings for ignored paths * Increased version to 1.19 * Added logs for refreshing cache to see if there is a concurrent call to update cache which leads to sequence errors * Added logs for refreshing cache to see if there is a concurrent call to update cache which leads to sequence errors * Added logs for refreshing cache to see if there is a concurrent call to update cache which leads to sequence errors * Added logs for refreshing cache to see if there is a concurrent call to update cache which leads to sequence errors
* update workflow to java 17 * Start next iteration with 1.1.20-SNAPSHOT * update maven plugin versions
* [release] Prepare release 1.1.20 * [skip ci] Start next iteration with 1.1.21-SNAPSHOT
* Increased version to 1.1.16 * Changed cors configuration to set disabled first to prevent cors configuration exceptions * Updated version to 1.17 * Replaced deprecated PostgreSQL94Dialect with PostgreSQLDialect * spring.jpa.open-in-view ist standardmäßig aktiviert: behoben * Excluded SecurityAutoConfiguration to prevent Spring from creating a default user * Changed SecurityConfiguration to allow access to swagger * Changed SecurityConfiguration to allow access to swagger * Excluded AutoConfiguration for UserDetailsService * Added RequestMatchers to address warnings for ignored paths * Increased version to 1.19 * Added logs for refreshing cache to see if there is a concurrent call to update cache which leads to sequence errors * Added logs for refreshing cache to see if there is a concurrent call to update cache which leads to sequence errors * Added logs for refreshing cache to see if there is a concurrent call to update cache which leads to sequence errors * Added logs for refreshing cache to see if there is a concurrent call to update cache which leads to sequence errors * Custom Sequence Generator not batch compatible #171
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.