Upgrade log4net to 3.3.0 and remove obsolete app.config files#1268
Merged
Conversation
claudiamurialdo
had a problem deploying
to
external-storage-tests
GitHub Actions
Failure
claudiamurialdo
temporarily deployed
to
kafka-integration-tests
GitHub Actions
Inactive
Collaborator
Cherry pick to beta success |
claudiamurialdo
temporarily deployed
to
kafka-integration-tests
GitHub Actions
Inactive
claudiamurialdo
temporarily deployed
to
external-storage-tests
GitHub Actions
Inactive
Collaborator
Cherry pick to beta success |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bump log4net from 2.0.11 / 2.0.15 to 3.3.0 in the GxClasses projects, and log4net.Ext.Json to 3.0.3 (compatible with log4net 3.x). Updated the hardcoded version in gxconfig.cs used by AssemblyResolve.
Removed app.config files from .NET Framework library projects: they are not read at runtime from a consuming executable, and the redirects were stale. No source changes needed — none of the APIs removed in log4net 3.0 are used in the codebase.
Issue:208361