1. Configure a Maven 2 proxy repo with policy RELEASE.
2. Add the Maven 2 proxy repo as a member to the public group.
3. Send the following request to a Nexus 2 public group containing a proxy repository member with policy RELEASE. Processing of the request is not handled by the RELEASE proxy repository as the path is detected as a SNAPSHOT request. Setting the logger remote.storage.outbound to DEBUG or processing the request with ?describe proves this:
1. Send the same request to a maven-public group with Release policy proxy repository ( ie. maven-central) as a group member and Nexus 3.2 sends the request outbound to the remote.
Setting the logger org.sonatype.nexus.httpclient.outbound to DEBUG proves this.
For consistency - request paths that are detected as SNAPSHOT related in Nexus 2 should also be treated as SNAPSHOT related in Nexus 3 - unless Nexus 3 has an improvement to make over Nexus 2.
SNAPSHOT requests should not be processed AT ALL by RELEASE policy repository group members in Nexus 3.x, whether they are hosted or proxy repositories.