Fix #1512: Plugin doesn't abort building an image in case Podman is u… #1585
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.
Fix #1512
In the previous version of this file the following if() was as follows. The methode isJson() checks by header (not by body):
In case the Podman daemon is used, the POST /build response is JSON and the HTTP status code is 200
as expected, but there is no header "Content-Type = application/json" nor "Content-Type" at all. Seen in
Podman 3.4.2. But the docker-maven-plugin relies on that JSON-body. In BuildJsonResponseHandler.process():
If no error is detected, the Maven-build goes on despite there was a problem building the
image!
The following if() first checks for the application/json Content-Type. If no Content-Type is set,
it tries to detect if the body is JSON. If so, the handler is called.