[PR] Fix KeyManage log when using CLI mode [jmeter]

["puiterwijk (via GitHub)" <gi...@apache.org>]

puiterwijk opened a new pull request, #6372:
URL: https://github.com/apache/jmeter/pull/6372

   Without this patch, whenever a KeyStore is used (for example for client certificates) in CLI mode, there is a message that no password was provided.
   This was caused by the else of the condition being on the wrong if statement, and can cause people to spend a lot of time trying to debug why the key store won't work.
   
   ## Types of changes
   - Bug fix (non-breaking change which fixes an issue)
   
   ## Checklist:
   <!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
   <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
   - [X] My code follows the [code style][style-guide] of this project.
   - [ ] I have updated the documentation accordingly.
   
   [style-guide]: https://wiki.apache.org/jmeter/CodeStyleGuidelines
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Fix KeyManage log when using CLI mode [jmeter]

["vlsi (via GitHub)" <gi...@apache.org>]

vlsi merged PR #6372:
URL: https://github.com/apache/jmeter/pull/6372


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org