Release ngrinder-3.5.4 · naver/ngrinder

Changes
- Release new experimental HttpClient based on apache httpcomponents-core
  - Support modern HTTP specification
  - Provide easy-to-use APIs
  - See new nGrinder HTTP client guide
- Use controller DNS instead of IP to support agent-controller reconnection in cloud env
- Support script template customization
  - Each ngrinder admin can deploy customized script template under ${NGRINDER_HOME}/script_template
- Provide the connection reset option in test configuration page
  - If you turn it on, it tries to reuse connection as much as possible.
- Bump Jython standard up to 2.7.2
- Bump internal used Junit up to 4.13.1
  - nGrinder no longer depends on specific version of junit for performance test
Notice
- If you have a trouble with updating controller from ngrinder 3.4.X to a newer version. Please refer to How to update ngrinder controller
Bug fix
- #706 Cancel progressing state test when starting controller
- #714 Fix validation error when using AppClassLoader in over JDK9
- #716 Fix script validation error in windows
- #731 Fix not working remember-me
- #739 Fix easy clustering
- #745 Make compatibility with IE11
- #748 Make grinder utils work on Jython performance test
- #773 Fix cannot search user with two characters
- #774, #779 Fix duplicated running test on one user

Provide feedback