aglinxinyuan commented on PR #6183: URL: https://github.com/apache/texera/pull/6183#issuecomment-4888268718
### Test result Tested this change — it fails to build. Documenting the evidence here. **Build / resolution:** every Scala job on this PR is red. It never reaches compilation — it dies at dependency resolution, because with `scalaVersion := 3.8.4` sbt cross-versions `%%` deps to the `_3` suffix: ``` [error] sbt.librarymanagement.ResolveException: Error downloading org.scalamock:scalamock_3:5.2.0 [error] not found: https://repo1.maven.org/maven2/org/scalamock/scalamock_3/5.2.0/scalamock_3-5.2.0.pom [error] (DAO / update) ... ``` (from `build / amber (ubuntu-latest, 17)` — https://github.com/apache/texera/actions/runs/28757106646/job/85266005899) **Root cause, verified against Maven Central:** | Artifact | Exists? | |---|---| | `org.scalamock:scalamock_3:5.2.0` | ❌ 404 | | `org.scalamock:scalamock_2.13:5.2.0` | ✅ 200 | scalamock (declared in `amber/build.sbt` and `access-control-service/build.sbt`) has no `_3` artifact at 5.2.0, so resolution can't complete. And that's only the first blocker — the diff flips the compiler from Scala 2.13 to Scala 3, so greening this would require porting the entire amber + platform codebase to Scala 3, not bumping a dependency. **Conclusion:** not mergeable as a dependency update. Closed above via `@dependabot ignore this major version`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
