update 9298 with master #2872
Merged
update 9298 with master #2872
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
…serebelo/liquibase into joserebelo-foreign-key-constraint-exists
…callers to correctly obfuscate secure values.
# Conflicts: # liquibase-cli/src/main/java/liquibase/integration/commandline/LiquibaseCommandLine.java # liquibase-core/src/main/java/liquibase/integration/commandline/Main.java # liquibase-core/src/main/java/liquibase/logging/core/DefaultLogMessageFilter.java
Remove custom log message filtering
…ow duplicate foreign key definitions
…serebelo/liquibase into joserebelo-foreign-key-constraint-exists
…ers return FilteredReactiveWebContextResources (#2758) * Fix Additional unfixed issues with relativeToChangelogfile + logicalFilePath * Extracted the use of the DefaultResourceLoader to a single construction and within an overridable method * Handle null value passed to SpringResourceAccessor constructor Co-authored-by: Nathan Voxland <nathan@voxland.net>
- Moved liquibase-managed CLI libraries to internal/lib - Removed version from libraries added to internal/lib - Moved classpath creation logic from batch/bash scripts to new LiquibaseLauncher class that wraps LiquibaseCommandLine - Added library version info to the --version output
* Fix ForeignKeyComparator when foreign key table is not known * Added integration test for foreignKeyExists precondition without a tableName set * Fixed fk exists test to work with databases like hsql which don't allow duplicate foreign key definitions Co-authored-by: Nathan Voxland <nathan@voxland.net>
Updated changelog.txt for 4.11.0
- Removed reflection-based blacklisting of `sun.net.www.protocol.http.HttpURLConnection` in favor of the new logChannels white list
Added whitelist for CLI log channels to include
suryaaki2
approved these changes
May 24, 2022
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.
Environment
Liquibase Version:
Liquibase Integration & Version: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.>
Liquibase Extension(s) & Version:
Database Vendor & Version:
Operating System Type & Version:
Pull Request Type
Description
A clear and concise description of the issue being addressed. Additional guidance here.
Steps To Reproduce
List the steps to reproduce the behavior.
Actual Behavior
A clear and concise description of what happens in the software before this pull request.
Expected/Desired Behavior
A clear and concise description of what happens in the software after this pull request.
Screenshots (if appropriate)
If applicable, add screenshots to help explain your problem.
Additional Context
Add any other context about the problem here.
Fast Track PR Acceptance Checklist:
Need Help?
Come chat with us in the Liquibase Forum.