Prevent NullPointerException in ResourceImageBoth if cannot initialize JAR retrieval #169
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
…JAR retrieval I firstly started from annotating the methods and throwing IOException, but then decided to do a proper error propagation instead. It smells like a real issue though there is no relevant bugtracker entries.
oleg-nenashev
commented
Jun 20, 2017
| } | ||
| return null; |
There was a problem hiding this comment.
NPE will happen in f.isDone() (line 30)
|
This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation. |
jglick
approved these changes
Jun 21, 2017
|
@reviewbybees done |
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.
I firstly started from annotating the methods and throwing IOException, but then decided to do a proper error propagation instead.
It smells like a real issue though there is no relevant bugtracker entries.
@reviewbybees