-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade logging-parent
to version 11.3.0
#2963
Closed
ppkarwasz
wants to merge
11
commits into
fix/2.x/2937-http-watcher
from
feature/2.x/logging-parent-11.3.0
Closed
Upgrade logging-parent
to version 11.3.0
#2963
ppkarwasz
wants to merge
11
commits into
fix/2.x/2937-http-watcher
from
feature/2.x/logging-parent-11.3.0
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
MongoDB is a binary server. The current `log4j-mongodb` tests download a **generic** binary MongoDB distribution and try to run it. The distribution is not self-contained and requires several libraries (e.g., OpenSSL) to be available on the target host. Those libraries are not always available in the required version: e.g., currently MongoDB needs OpenSSL 1, but OpenSSL 3 is bundled in the most recent Debian. This PR switches from the binary distribution to the usage of the **latest** Docker image available. The advantages of this approach are: - We always test against the newest server version available. - The success of the tests does not depend on the libraries installed on the host. - Tests can run in parallel. In the current approach, parallel tests failed since each one tried to download MongoDB separately. The main disadvantage is that Docker will be required to test `log4j-mongodb`. This is the case for the CI, but individual developers might need to install it too. Co-authored-by: Volkan Yazıcı <volkan@yazi.ci>
ppkarwasz
force-pushed
the
feature/2.x/logging-parent-11.3.0
branch
from
September 22, 2024 08:31
9127152
to
149dbe7
Compare
Merged in 93483ef |
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.
This PR upgrades to the latest version of
logging-parent
.It's target branch is #2941 and should be merged after it (and after
logging-parent
11.3.0 is released).It includes 3 additional changes:
transitive
modifier from optional dependencies #2930. The newlogging-parent
already uses version 4.docker
profile in CI forlog4j-layout-template-json-test
#2953,All these changes involve only tests, by improving them. E.g. the MongoDB integration tests no longer use an old (possibly deprecated) version of MongoDB, but the latest compatible with the driver.