Blog com notícias sobre, Linux, Android, Segurança , etc

Summary This release hardens the Sandbox feature introduced in 1.4.0, focusing on observability, cache isolation, and correctness of snapshot reuse. Sandbox activity logging makes it easier to tra...

Witness is a pluggable framework for software supply chain risk management. It automates, normalizes, and verifies software artifact provenance. - in-toto/witness

Summary Support for PMD 7.29.0 What's Changed in 1.7.2 Clean up Javadoc in 828c6ed Bump PMD to version 7.29.0 in 5874215 Full Changelog: 1.7.1...1.7.2

Summary Support for JaCoCo 0.8.16 What's Changed in 1.1.1 Bump JaCoCo to version 0.8.16 in 7d9673e Full Changelog: 1.1.0...1.1.1

Summary Added support for PMD 7.28.0 with new auxClassPath() and addClassPath(String...) methods Migrated to JSpecify for nullability contracts Improved input validation Added CLI arguments to dis...

Summary Implemented an isolated, per-extension sandbox for downloading dependencies, Fixed ObjectTools sign-check methods (requirePositive, requireNegative, requireNonNegative) to reject NaN and t...

## Introduction After bazel-bootstrap 7.7.1 was landed into Debian unstable, I'm working on packaging newer Mozc (Most famous Japanese input method editor) with Bazel. Here is the blog entry initial efforts to build Mozc with Bazel at that time. kenhys.hatenablog.jp Then, I've shared implementing PoC `dh-bazel` experiment. See why dh-bazel is needed, and prototype about `dh-bazel`. kenhys.hatenablog.jp As a Bazel beginner, want to know what should pass to Bazel, what should not pass to Bazel. ## What is improved in recent dh-bazel? In the previous versions of `dh-bazel`, it supports only basic features to build with Bazel as a thin wrapper. %: dh $@ --buildsystem=bazel override_dh_auto_build: dh_auto_build -- //:hello Now, with recent changes, it supports the following environment variables to resolve required system libraries in dynamically. salsa.debian.org * `DH_BAZEL_OVERRIDE_MODULE` It search the specified modules from bundled dummy modules in `dh-bazel`. It accept ',' separated paramesters. (e.g. DH_BAZEL_OVERRIDE_MODULE=zlib,zstd) `dh-bazel` bundles abseil-cpp, apple_support, buildozer, lz4, openssl, protobuf, rules_android_ndk, rules_apple, rules_swift, zlib and zstd as dummy modules to linking system libraries. Now you can use it in `debian/rules` like this: #!/usr/bin/make -f # -*- makefile -*- # export DH_BAZEL_OVERRIDE_MODULE=zlib export DH_VERBOSE=1 %: dh $@ --buildsystem=bazel --without=single-binary override_dh_auto_build: dh_auto_build -- //:hello It is impossible to cover all of system libraries in Debian, so in that case, please consider to use the following `DH_BAZEL_PKGCONF_MODULE`. * `DH_BAZEL_PKGCONF_MODULE` It search the specified modules with pkgconf. It is useful when there is no bundled modules in dh-bazel if you want. It accept ',' separated paramesters. (e.g. DH_BAZEL_PKGCONF_MODULE=gtk4-x11,gtk4-unix-print). If DH_BAZEL_PKGCONF_MODULE could not match, then dh-bazel fallback to dig into `Build-Depends:` field in debian/control. Note that if it is not deterministic (e.g. -dev package provides multiple .pc files) dh-bazel gives up fallback with pkgconf. Now you can use it in `debian/rules` like this: #!/usr/bin/make -f # -*- makefile -*- # export DH_BAZEL_PKGCONF_MODULE=gtk4-x11,gtk4-unix-print export DH_VERBOSE=1 %: dh $@ --buildsystem=bazel --without=single-binary override_dh_auto_build: dh_auto_build -- //:hello ## Conclusion dh-bazel is still in very early stage prototype, but it resolves some sort of packaging glitches a bit by bit. I hope that it will help package maintainer using Bazel. (dh-bazel is not uploaded into debian/unstable yet, so stay tuned!)

Alongside the 3.0 release of bld, all extensions have been updated…

## Introduction After bazel-bootstrap 7.7.1 was landed into Debian unstable, I'm working on packaging newer Mozc (Most famous Japanese input method editor) with Bazel. Here is the blog entry initial efforts to build Mozc with Bazel at that time. kenhys.hatenablog.jp ## Why dh-bazel? After that, newer Mozc packages are uploaded into experimental and moved to testing phase on experimental now. mozc - Debian Package Tracker When started packaging efforts for newer Mozc with Bazel, I'm a newbie to do it. Now I've got a knowledge to do it a bit, I want to know best practice on packaging X on Debian with Bazel furturmore. Usually there are dh-X for buildsystem X on Debian, but it's not true for Bazel as far as I know. This is why I had started to write dh-bazel. I've wrote initial dh-bazel prototype and post a mail to debian-bazel ML. lists.debian.org dh-bazel supports the following way: %: dh $@ --buildsystem=bazel override_dh_auto_build: dh_auto_build -- //:hello If you want to build source under `src`, you could write d/rule like this: %: dh $@ override_dh_auto_build: dh_auto_build --buildsystem=bazel --sourcedirectory=src -- //:hello ## Conclusion dh-bazel is in very early stage prototype, but I have succeeded to build newer Mozc with some modifications to Mozc debian/rules on experimental with dh-bazel locally! dh-bazel is a thin wrapper for Bazel, so it does not reduce packaging glitches dramatically, but it helps some sort of packaging tasks IMHO. There are some achievement with dh-bazel * It helps to do similar building way like other debhelper buildsystem * It sets comprehensive Bazel startup options * It sets comprehensive Bazel command options * If you want to set extra flags, just specify it as additional user options (`--override_module=`, and so on) Note that it only simplify `dh_auto_build stage`, so you must manually install artifacts with .install or something correctly. I hope that it will help package maintainer using Bazel in the future. (dh-bazel is not uploaded into debian/unstable yet, so stay tuned!)

Summary Maintenance release improving null-safety contracts and strengthening input validation. What's Changed in 1.3.0 Migrate to JSpectify nullability contracts in [6ac05cd](https://github.[STRI...

Summary Migrates codebase to JSpecify nullability contract. Adds support for Spring Boot 4.1.0 with examples for 3.5.15 and 4.0.7. Refines WAR packaging to exclude buildDistDirectory and hardens v...

Summary Fix Windows file locking and invalid paths with atomic save (temp file + fsync + move). Migrate codebase to JSpecify nullability contracts. Align int/date calc behavior with Ant <propertyf...

Summary First stable 1.0.0 release with hardened execution and validation Migrated to JSpecify nullability contracts and added timeout / error handling Refactored JBangOperation to use ProcessExec...

Summary Migrates to JSpecify nullability contracts Adds validation tests for inputs and configuration Adds fluent report toggles: enableCsv/disableCsv, enableHtml/disableHtml, enableXml/disableXml...

Summary Migrates to JSpecify nullability contracts for strict null-safety Adds support for generating @Generated annotation Hardens validation for class names, extensions, and directories Improves...

Summary Support for Checkstyle 14,1,0 Migrated to JSpecify nullability contracts Refactored CheckstyleOperation to use shared tooling for classpath and command-line handling Improved input validat...

Summary Bumps PITest to 1.30.0 for latest features and fixes Migrates to JSpecify for explicit nullability contracts Refactors configuration handling to use repeated args for pluginConfiguration w...

Summary Updated Java Setup GitHub Action to v6 Migrated to JSpecify nullability contracts Refactored SourceSet and DokkaOperation for stricter validation, deterministic ordering, and cleaner CLI a...

Summary Migrate to JSpecify nullability contracts with @NonNull annotations Add --create-baseline CLI argument support Add @argfile support to handle Windows command-line limits over 30000 chars C...

Summary 1.2.0 is a safety, correctness, and modernization release Migrates API to JSpecify nullability with consistent validation Modernizes compiler execution via ProcessExecutor with env, timeou...

Fixed transitive dependencies resolving differently from Maven when a POM imports a BOM that manages the same dependency as a BOM imported by one of its ancestors. The POM's own import now wins, as...

Summary Made @RetryTest production-safe for parallel execution and fixes reporting/counting edge cases What's Changed in 1.1.1 Gate unused retries as disabled and include BeforeEach/AfterEach in...