playframework / playframework/play1
Upgrade com.ning:async-http-client to org.asynchttpclient:async-http-client
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 671
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
Play v1.7.1 still relies on an old version of AsyncHttpClient: https://github.com/playframework/play1/blob/1.7.1/framework/dependencies.yml#L21.
This library has moved from https://github.com/ning/async-http-client (last commit in 2016) to https://github.com/AsyncHttpClient/async-http-client.
Should we upgrade Play accordingly?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at framework/dependencies.yml line 21 and compare the current com.ning:async-http-client declaration with the org.asynchttpclient:async-http-client project named in the issue. Confirm the appropriate replacement coordinates and version, then update the dependency so Play uses the newer artifact and verify the dependency configuration resolves successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100