Open drmercer-lucid opened 2 years ago
As a workaround, it may be helpful to use the custom launcher script option: https://github.com/salesforce/rules_spring/blob/master/springboot/bazelrun.md#custom-launcher-script
until we resolve this (which appears to be a variant of #110 as you mentioned).
As a workaround, it may be helpful to use the custom launcher script option:
Unfortunately, this failure seems to happen in the script that launches the (possibly custom) launcher script. This is the source of the script that's failing (the atlassian-embed_deploy
script in the error above):
I've worked around this by just downgrading to 2.0.0, so this isn't urgent. :slightly_smiling_face: Just something that ideally would be fixed so we can upgrade without losing ibazel. I'll take a stab at debugging it myself with a local clone of rules_spring, if I have time.
Hi team,
We have a Spring server built using bazel, and we use
ibazel
for local development.ibazel run //atlassian-embed
should run the Spring server and automatically restart when any of the source files change. This was working great on rules_spring 2.0.0, but after upgrading to 2.1.0 or higher,ibazel run
fails with these errors:(Where
[bazel-bin]
is the full path of thebazel-bin
dir.) Looking at the release notes for 2.1.0, I see some changes were made around the run script; I'll look into those and see if I can find a fix, but figured it'd be worth opening this anyway in case anyone else runs into this issue.