-
Notifications
You must be signed in to change notification settings - Fork 1
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
Artipie http3 test #13
Artipie http3 test #13
Conversation
MatcherAssert.assertThat("Maven install is not successful", exec.getExitCode() == 0); | ||
MatcherAssert.assertThat( | ||
res, | ||
Matchers.stringContainsInOrder( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can it prove that the packages were gotten by HTTP 3?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a) https://artipie:8091/my-maven-proxy
- is a path to artipie http3 repository
b) is such configuration maven client can perform request over http3 only (it fails trying to get dependency from central over http 1)
So there are only 2 possibilities in current configuration: either build is success and deps were obtained via http3 or it fails
@dgarus I've corrected logs and assertion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Added integration test for plugin and artipie, also:
InputStream
(viaInputStreamResponseListener
) instead of byte array after gettingbuffering capacity exceeded
error for some heavy jar