[dimejiogunyoye]

Fix CI build failure after bumping gateway-framework to 2.7.0

Problem

After gateway-framework was bumped from 2.6.0 to 2.7.0 (#59), the “Build with Maven” step failed during dependency resolution:

Path com/diffusiondata/gateway/gateway-framework/2.7.0/gateway-framework-2.7.0.jar NOT allowed from push-repository

Cause

Recent Maven Resolver versions auto-discover a .meta/prefixes.txt file on each remote repository and refuse to fetch any path not listed in it. The prefixes file on https://download.diffusiondata.com/maven/ is stale (or doesn't exist): it doesn’t include com/diffusiondata/gateway, even though the repository serves those artifacts.

2.6.0 kept working only because it was restored from the ~/.m2 cache, so it never reached the filter. 2.7.0 isn’t cached, so it was blocked.

The “Update dependency graph” step confirms the cause. Its newer resolver checks the denied path, finds the artifact, and logs:

Remote repository push-repository serves path com/diffusiondata/gateway/gateway-framework/2.7.0/gateway-framework-2.7.0.pom that its auto-discovered prefixes file denies; the prefixes file appears stale.

Fix (workaround)

Set MAVEN_OPTS: -Daether.remoteRepositoryFilter.prefixes=false at job level in .github/workflows/maven.yml, so it applies to both the build and the dependency-graph steps.