Manuel Sugawara

+1 this is a [bug report](https://github.com/aws/aws-sdk-java-v2/issues/4604) for the `S3Presigner.java` mentioned by @tpetillot. Here is a small reproducible test case that breaks with Scala 2. Using the following Java interfaces and...

A more general approach was implemented in this [PR](https://github.com/awslabs/smithy/pull/1534). You can look at the docs for how to do either [inclusion](https://smithy.io/2.0/guides/building-models/build-config.html#includeshapesbyselector) or [exclusion](https://smithy.io/2.0/guides/building-models/build-config.html#excludeshapesbyselector) of shapes using a selector.

We are aware that the rule is too restrictive and we are planning to publish an RFC in the coming weeks to allow these and URIs that _might conflict_ at...

I have opened a [draft pull request](https://github.com/awslabs/smithy/pull/1539) for our current thinking about how to remove this restriction, if you have time we will appreciate your feedback on this proposal

The RFC has been merged and the implemented in Smithy, see the [updated docs here](https://smithy.io/2.0/spec/http-bindings.html#specificity-routing). Apologies for the late notice, I forgot about updating this thread.

We will analyze how to work around this issue, one idea would be to add an special suppression that allows to say: "don't validate the URIs for conflicts, the service...

Hi @ericxinzhang, thank you for reaching out. The changes mentioned were partially reverted [here](https://github.com/awslabs/smithy/commit/380449d2df8410342507f575638921fb5f660814) for the reasons explained in the commit message. Not sure what to do about properly handling...

> Does that mean all resource operations in a given service closure should have the same URI ? 😕 No, it does mean that the two patterns * `/dc/labor/shift-planning/v1/input/{screenId}/tabs` *...

I have submitted a [draft pull request](https://github.com/awslabs/smithy/pull/1539) for our current thinking about how to relax this restriction, if you have time we will appreciate your feedback on this proposal

Apologies for not updating this issue before, we have released specificity routing which allows those URI to coexist. See the [documentation here](https://smithy.io/2.0/spec/http-bindings.html#specificity-routing).