search

salesforce / rules_spring

Bazel rule for building Spring Boot apps as a deployable jar
BSD 3-Clause "New" or "Revised" License
224 stars 49 forks source link

WARNING: moving maven_jar() support to a maintenance branch #26

Closed plaird closed 3 years ago

plaird commented 4 years ago

NOTE: If you are importing this rule with git_repository() and only specify the master branch (not commit id) you will break soon. I plan to remove support for maven_jar() in the master branch since it no longer exists in Bazel 2.0. Please rewrite your import to use a git commit id.

Plan: We have a couple of work items in flight: https://github.com/salesforce/bazel-springboot-rule/projects/1

After those are merged, I plan to cut a ceremonial 1.0 release. We don't actually release binaries, so it isn't a real release, but most importantly I will cut a 1.x branch. maven_jar() usage will travel there.

master branch will soon after migrate away from maven_jar, see #7

I hope to support maven_install and jvm_maven_import_external in parallel in master, but it will require moving some furniture around. Protect your CI build by using git_repository() with a commit id, so you can manage any necessary changes at your leisure.

plaird commented 4 years ago

I have been entirely consumed by internal projects, and some work on Bazel Eclipse Feature, so I haven't had time to do this maintenance work. I still plan to get to this.

plaird commented 3 years ago

This was done on September 29, 2020