update the dependency to the bouncycastle project from "-jdk15on" jars to "-jdk18on:1.76" jars #906
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
…dy/bmp/proxy/newHarTest.groovy testCaptureResponseCookiesInHar()
kazurayam
changed the title
This was referenced Nov 7, 2023
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.
See kazurayam#5 for the detail of what I have done.
The O'Reilly book "Hands-on Selenium WebDriver with Java", Chapter 9 shows a sample code 9-4 that uses BrowserMob Proxy together with WebDriverManager. Unfortunately the sample code sometimes fails, because both products depend on the bouncycastle.org products, but different series of jar.
For example, BrowserMob Proxy depends on
org.bouncycastle:bcprov-jdk15on; but WebDriverManater depends onorg.bouncycastle:bcprov-jdk18on. This difference causes the Example 9-4 to fail with messagejava.lang.NoSuchFieldError: id_RSASSA_PSS_SHAKE128
In order to resolve this problem, I updated the pom.xml files of browsermob-proxy project so that it depends on the newer jars named
-jdk18on.