bazelbuild/[email protected]

[publish-to-bcr-bot]

Release author: @comius.

Automated by Publish to BCR.

[fmeum]

@comius Looks like the @ in https://github.com/bazelbuild/rules_java/blob/e4a3f07d41048e951c5305f6304da9ec29bb81f5/BUILD#L15 and https://github.com/bazelbuild/rules_java/blob/e4a3f07d41048e951c5305f6304da9ec29bb81f5/java/BUILD#L9-L10 could (and have to) be dropped.

[meteorcloudy]

@comius To avoid going back and forth like this, you probably want to test rules_java before cutting a new release. You can set up a simple test like this:
#269 (comment)

[comius]

@comius To avoid going back and forth like this, you probably want to test rules_java before cutting a new release. You can set up a simple test like this: #269 (comment)

I did something similar.

Before, I didn't expect differences in the behaviour between running build //... in the repo and running @rules_java//....

[comius]

You can close this one now.

[comius]

PS. Publish to BCR failed with 5.3.5, I pinged Derek