Update dependency rules_spring to v2.6.2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
rules_spring	http_archive	minor	2.2.0 -> 2.6.2

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

salesforce/rules_spring (rules_spring)

v2.6.2: Jan 2025 Fix git.properties

Compare Source

This release contains a single bug fix.

The 2.5.2 release introduced the ability to have multiple springboot() macros in the same package (#​139). To support this feature, the rule prefixes the generated names in the macro to prevent filename/target collisions. Unfortunately, this broke support for the git.properties file in Spring Boot because it loads the file based on name. With the prefixing the filename became mytarget_git.properties which is ignored by Spring. This release fixes that problem (#​259). In addition to fixing the bug, tests were added to detect file packaging problems in the future.

Another improvement was recently added to rules_spring. It is a new example, and so is not present in the release jar. But it is worth mentioning here that there is now an example for BuildProperties (#​113) support in Spring Boot applications.

Bzlmod:

bazel_dep(name = "rules_spring", version = "2.6.2")

WORKSPACE:

http_archive(
    name = "rules_spring",
    sha256 = "a1305e2283fea77ebe2aa29dd03ffb2ac8c248b9a3d1d7fd28ff6478962dd27b",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.6.2/rules-spring-2.6.2.zip",
    ],
)

v2.6.1: Dec 2024 Bug Fixes for Multiarch, JAVABIN, debug

Compare Source

This release fixes a few issues:

• springboot rule is now preconfigured for multi-arch oci use cases #​250 (thanks for report @​code-weirdo)
• the JAVABIN environment variable is now a step in the precedence order for finding the JVM for bazel run commands #​245
• fixed the springboot rule environment variable name for debug logging (is it now properly upper cased) #​148

Bzlmod:

bazel_dep(name = "rules_spring", version = "2.6.1")

WORKSPACE:

http_archive(
    name = "rules_spring",
    sha256 = "98143672b2edd2eb84762a6ebe6afc3a194d1ec06bdfaaf0cc87d4d750476db0",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.6.1/rules-spring-2.6.1.zip",
    ],
)

v2.6.0: Dec 2024 Bazel Run Configuration Enhancements

Compare Source

This release improves configuration options for services launched via bazel run.

• Added support for externalized configuration by loading application.properties files passed in the bazelrun_data attribute. See docs for details. #​135
• Added support for passing environment variables into the bazel run launcher script, which can be used to set Spring properties. See docs for details. #​166
• Fixes a bug whereby only the first datafile passed in the bazelrun_data array attribute was processed #​238

Bzlmod:

bazel_dep(name = "rules_spring", version = "2.6.0")

WORKSPACE:

http_archive(
    name = "rules_spring",
    sha256 = "b8c2de8a8123906c9d0fc5afd35dfde5f55d6030c4d72266e4dfd0543f621d89",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.6.0/rules-spring-2.6.0.zip",
    ],
)

v2.5.2: Dec 2024 Multi-target support, Bazel Run JVM Flag Improvements

Compare Source

This release eliminates a couple of limitations in the springboot() macro. The first is the most notable:

• Support multiple springboot targets in a single BUILD file; eliminates the limitation of having at most one #​139

And an enhancement, and a bug fix, related to JVM flags used during Bazel run executions of springboot() targets:

• Added new attribute bazelrun_jvm_flag_list as the new preferred form of bazelrun_jvm_flags. It has the same purpose but is more bazel-like: it is an array of JVM args, instead of a space separated string. bazelrun_jvm_flags is now deprecated. #​234
• Discovered that ADD_OPENS and ADD_EXPORTS Bazel run script variables were not working correctly in some cases. There was no delimiter between ADD_OPENS and JVM_FLAGS in the arg list and so in some cases jvm flags were being mistaken for adds. This didn't cause any actual problems because they just get appended together on the command line in the end, but it was messy. I removed those two variables since ADDs can just be specified together as additional JVM_FLAGS in a single list. This will only impact users that have custom launcher scripts - please refresh your launcher script with updates from the default one. #​234

Bzlmod:

### rules_spring is not in Bazel Central Registry yet, so use the specific commit
bazel_dep(name = "rules_spring", version = "2.5.2")
git_override(
    module_name = "rules_spring",
    remote = "https://github.com/salesforce/rules_spring",
    commit="9458a305f2978673cdeb26962d38fd0d4f7b7ad7",
)

WORKSPACE:

http_archive(
    name = "rules_spring",
    sha256 = "e08254a8dac77b1d3f85ada556038605c4106dbf09f92f26a06df511d16e6471",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.5.2/rules-spring-2.5.2.zip",
    ],
)

v2.5.1: Dec 2024 Bzlmod fix, bazelrun script fixes

Compare Source

This is a bug fix release:

• Fixes an error in the Bzlmod MODULE.bazel of 2.5.0 related to the dev dependency rules_jvm_external #​229
• Fixes an issue with the bazelrun script, due to the first line being a blank line #​143 (@​drmercer-lucid)
• Fixes a packaging problem with the bazelrun script when --nolegacy_external_runfiles is used #​227 (@​drmercer-lucid)
• Stood up a public test repo for testing rules_spring releases; previously we relied on an internal monorepo for all testing. This will allow us to innovate with rules_spring faster.

Bzlmod:

### rules_spring is not in Bazel Central Registry yet, so use the specific commit
bazel_dep(name = "rules_spring", version = "2.5.1")
git_override(
    module_name = "rules_spring",
    remote = "https://github.com/salesforce/rules_spring",
    commit="29e7be015415b1a80e706cf40e333b1a6251961b",
)

WORKSPACE:

http_archive(
    name = "rules_spring",
    sha256 = "fe247b8b8bd58c82023e0b4212484724bf17f81394f97e913c522cea68b125e8",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.5.1/rules-spring-2.5.1.zip",
    ],
)

v2.5.0: Dec 2024 Transition to Bzlmod

Compare Source

Fully transitioned to Bzlmod for workspace dependency management. MODULE.bazel now fully describes the workspace dependencies, and WORKSPACE has been deleted.

NOTE: this release has a bug in the MODULE.bazel file, and is not recommended for use. Use 2.5.1 instead.

If you are just starting your Bzlmod journey, here are some good starting points:

• Bzlmod official docs
• Bzlmod migration journey blog series

Bzlmod:

### rules_spring is not in Bazel Central Registry yet, so specify the 2.5.0 commit
bazel_dep(name = "rules_spring", version = "2.5.0")
git_override(
    module_name = "rules_spring",
    remote = "https://github.com/salesforce/rules_spring",
    commit="168362d1a70a2f032700f77498aa4d3d863ff144",
)

WORKSPACE:

http_archive(
    name = "rules_spring",
    sha256 = "5a4f83c892ac072088e4a03d3647c8282f782b097a33bdb01723c63ae930311d",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.5.0/rules-spring-2.5.0.zip",
    ],
)

v2.4.2: Dec 2024 rules_license and Bazel Constraint Attributes

Compare Source

This release adds a few minor features:

• Adds support for restricted_to and target_compatible_with attributes (Bazel standard attributes) #​219 (@​bhnord)
• Adds official license targets using rules_license #​222 and #​223

To use this release:

Bzlmod:

  bazel_dep(name = "rules_spring", version = "2.4.2")
  git_override(
      module_name = "rules_spring",
      remote = "https://github.com/salesforce/rules_spring",
      commit="23b0fb07c56820f0d576b24a8879841f4165b568",
  )

WORKSPACE:

http_archive(
    name = "rules_spring",
    sha256 = "95e0bc66b8d3424cddbe37ca75babff372a8f80c833d5dce6e87277476a9b97c",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.4.2/rules-spring-2.4.2.zip",
    ],
)

v2.4.1: Dec 2024 Better Deps Filter

Compare Source

This release does not change the rule implementation, but contains two good enhancements:

• We have overhauled how to eliminate unwanted dependencies. The new deps_filter_transitive filter has the same behavior as the deps_exclude attribute, but also applies to the classpath used in tests so is more accurate. #​171
• Fixed an issue with extraneous files in the release zip file. #​212

To use this release:

http_archive(
    name = "rules_spring",
    sha256 = "939dd1399ff75a067a20aeeef2000c3a37791e54c8c5a899e78bd8175341263a",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.4.1/rules-spring-2.4.1.zip",
    ],
)

v2.4.0: Oct 2024 Minor Enhancements

Compare Source

This is a minor release.

• Feature: fail build by default if junit/mockito in deps #​207
• Bug: Fix non-determinism in build-data.properties file #​205 (thanks @​jpgxs)
• Feature: add jartools_toolchains attribute for an obscure use case #​209

To use this release:

http_archive(
    name = "rules_spring",
    sha256 = "c99a54db3e86ee3a5ff2cdd545824ec1d3d41f72644ca48283218ce56190b3b1",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.4.0/rules-spring-2.4.0.zip",
    ],
)

v2.3.2: Mar 2024 Support for add-opens and add-exports

Compare Source

This will assist users migrating to JDK17 and beyond, as they will sometimes be impacted by stricter Java modularization enforcement.

The JDK has two mechanisms for loosening those restrictions described here:

1. add-exports
2. add-opens

For example: To add add-opens and add-exports for a springboot target.

springboot(
  name = "ordering-service",
  boot_app_class = "com.salesforce.services.ordering.OrderingService",
  java_library = ":base_lib",
  bazelrun_addopens = ["java.management/sun.management=ALL-UNNAMED"],
  bazelrun_addexports = ["java.base/java.base=ALL-UNNAMED"],
)

To use this new release, add this section to your WORKSPACE file:

http_archive(
    name = "rules_spring",
    sha256 = "87b337f95f9c09a2e5875f0bca533b050c9ccb8b0d2c92915e290520b79d0912",
    urls = [
        "https://github.com/salesforce/rules_spring/releases/download/2.3.2/rules-spring-2.3.2.zip",
    ],
)

v2.3.1: Jan 2024 Support for Spring Boot 3.2.0

Compare Source

The features for this release come from Knut Eirik Leira Hjelle @​hjellek (Takk skal du ha!).

These features target support for Spring Boot 3.2.0. Both relate to the new nested jar support.

• Support for configuring the Boot Loader with the new boot_launcher_class rule attribute. This was a missing feature in general, and specifically is important for Boot 3.2.0 to use the new org.springframework.boot.loader.launch.JarLauncher #​177
• Support the NestedFileSystemProvider (internal packaging change, not user visible) #​176

v2.3.0: Nov 2023 Bazel Run use Java Toolchain, and Javax->Jakarta Migration Support

Compare Source

This release provides two enhancements.

What's Changed

Bazel Run Launch JVM

The springboot rule has been updated such that the JVM used to launch the service from bazel run will now use the JVM from the current java toolchain in the workspace, by default. This replaces the previous default behavior, which was to use JAVA_HOME.

In addition, there are two new options for overriding this behavior. See the launcher JVM docs for more details.

Javax => Jakarta Migration Support

This release includes a new javax detector that is not enabled by default. It detects any jar in the springboot dependency graph that contains a class from a javax package. It consults an ignorelist (that you provide) to determine if this is known jar. If not, it will fail the build.

If you haven't heard of the javax -> jakarta migration that is up-ending the Java community, this may seem like a strange feature. For more information, please see our new docs on this topic. The javax -> jakarta migration (which is required for Spring Boot 3), and the new detector feature, are explained there.

v2.2.4: July 2023 Optionally omit git.properties in resulting jar

Compare Source

What's Changed

• provide mechanism to not include git.properties file in resulting jar by @​kriscfoster in https://github.com/salesforce/rules_spring/pull/168

Full Changelog: salesforce/rules_spring@2.2.3...2.2.4

v2.2.3: June 2023 Support Propagating Visibility of Springboot Jar

Compare Source

This release provides the ability for the springboot target to reside in a different package from another rule that uses it. This previously wasn't possible due to the visibility not being propagated.

What's Changed

• release of 2.2.2 by @​plaird in https://github.com/salesforce/rules_spring/pull/162
• propagate visibility for springboot jar by @​kriscfoster in https://github.com/salesforce/rules_spring/pull/164

New Contributors

• @​kriscfoster made their first contribution in https://github.com/salesforce/rules_spring/pull/164

Full Changelog: salesforce/rules_spring@2.2.2...2.2.3

v2.2.2: January 2023 Support for Addins Feature

Compare Source

This release provides a small feature to allow the developer to add arbitrary files to the root of the generated springboot jar. For example, this feature can be used to add a license file to the generated jar. This is accomplished by using the new addins attribute:

addins = [":info.txt", ":author.txt"],

The files are then added into the generated springboot jar:

jar -tvf bazel-bin/examples/demoapp/demoapp.jar | grep .txt
   132 Fri Jan 01 00:00:00 PST 2010 info.txt
    11 Fri Jan 01 00:00:00 PST 2010 author.txt

(Note: if you pulled the release on the first two days, you got a botched zip file that didn't actually include the new feature. I fixed the package on Jan 30. That changed the SHA. Apologies if that broke you)

v2.2.1: April 2022 Support for Bazel's testonly attribute

Compare Source

The Bazel standard testonly attribute is now accepted by the springboot macro, and applied to the generated subrules. This is to support the use case of a springboot application used for integration testing, which needs to depend on Java libraries that are marked testonly. #​144

Also, the default branch of this repository is now main instead of master, to comply with modern Git standards. The master branch will be deleted sometime in the future. If you pull the this repository into your workspace using a git_repository rule with branch, make sure to switch to main.

---

Configuration

📅 Schedule: Branch creation - "before 5am every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.