[7.1.0] Remove user specific path from the lockfile (Fixes #19621) (#21009)
If a local registry is specified using a workspace placeholder, the lockfile stores location details of the files with resolved workspace information, including user-specific paths. To fix that: Updating the logic to use the workspace placeholder %workspace% during lockfile writing and reverting to the resolved paths when reading. PiperOrigin-RevId: 600876401 Change-Id: I6162d8e8f1fe5e29b7899fc5bb218d1b6be926d0
Showing
- src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelLockFileFunction.java 5 additions, 3 deletions...evtools/build/lib/bazel/bzlmod/BazelLockFileFunction.java
- src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelLockFileModule.java 2 additions, 1 deletion.../devtools/build/lib/bazel/bzlmod/BazelLockFileModule.java
- src/main/java/com/google/devtools/build/lib/bazel/bzlmod/GsonTypeAdapterUtil.java 14 additions, 9 deletions.../devtools/build/lib/bazel/bzlmod/GsonTypeAdapterUtil.java
- src/test/py/bazel/bzlmod/bazel_lockfile_test.py 27 additions, 4 deletionssrc/test/py/bazel/bzlmod/bazel_lockfile_test.py
Please register or sign in to comment