You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#771 enabled manifest stamping by default. This results in mutating third-party jars (which breaks SBOM verification) as well as inserting a "processed_" prefix in all file names. My deployments began failing because other non-Bazel projects cannot locate jars by name such as "commons-foo-1.2.3.jar" at runtime.
In the meantime, I can move forward by adding a --@rules_jvm_external//settings:stamp_manifest=false on the cmdline. However, as it involves mutating and renaming third-party artifacts, IMO manifest stamping should never be the default.
The text was updated successfully, but these errors were encountered:
Similar to JetBrains/bazel-bsp#403, the Bloop compiler also expects to find a jar file that starts with scala-compiler. Could the stamping be changed to create the unstamped files as unprocessed_*.jar and then the final files could have the canonical file name without a prefix?
#771 enabled manifest stamping by default. This results in mutating third-party jars (which breaks SBOM verification) as well as inserting a "processed_" prefix in all file names. My deployments began failing because other non-Bazel projects cannot locate jars by name such as "commons-foo-1.2.3.jar" at runtime.
In the meantime, I can move forward by adding a
--@rules_jvm_external//settings:stamp_manifest=false
on the cmdline. However, as it involves mutating and renaming third-party artifacts, IMO manifest stamping should never be the default.The text was updated successfully, but these errors were encountered: