apache-client is still being included by default in aws clients

[patrickjamesbarry]

Now that apache5-client is available, I would have thought that would become the new default. But rather the outdated 4.x version is being used/included by default. If you use mvn dependency:tree when pulling in a dependency like software.amazon.awssdk:elasticloadbalancing:2.41.8

[INFO] +- software.amazon.awssdk:elasticloadbalancing:jar:2.41.8:compile
[INFO] | +- software.amazon.awssdk:aws-query-protocol:jar:2.41.8:compile
...
[INFO] | +- software.amazon.awssdk:apache-client:jar:2.41.8:runtime

You can see this runtime dependency will still be used, even if you are specifiying the new apache5-client. You have to explicitly exclude the old jar to not have it get bundled. Is this expected behaviour? We need our jars as small as possible as we deploy aws java lambdas.

[dagnir]

Hi @patrickjamesbarry, thanks for sharing your interest in the apache5-client! You're right that we have not yet swapped the older apache-client for apache5-client as the default sync HTTP client. Eventually we want this to be the case, but we are still in the planning phase for how best to make that change; we want to ensure that when we switch over, that it does not cause issues or disruptions for anyone.

If you have switched to from apache-client to apache5-client I would like to hear about your experience! This would definitely help inform this planning process.

[patrickjamesbarry]

I know you guys previewed apache5-client for 6+ months. I would think that would have flushed this out enough to be have some confidence in moving off of the old apache client. By doing it this way, you are making consumer pollute their poms with changes like:

[dagnir]

Thanks for the feedback! I agree that needing to exclude the older client is not ideal; however we felt a staged approach would be safer, especially when switching such a critical default component. For future feature/component rollouts, we will keep this in mind.

On a related note, we merged #6676 recently, which takes us one step further to removing the older apache-client.