Switch java_proto_library & java_grpc_library

[vorburger]

Use https://grpc.io instead of https://rules-proto-grpc.com (fixes #202)

🪄 🧛🏽

[vorburger]

CI Build is red due to bazel-bin/connectors/demo/demo --singlejar 9090 failing to start.

It's bad that ./test.bash does not detect that - I'll try to fix both the missing test coverage and actual problem.

[vorburger]

CI Build is red due to bazel-bin/connectors/demo/demo --singlejar 9090 failing to start.

Actually not exactly, what was broken here was the following (and I'm glad CI detected it):

$  bazel-bin/connectors/demo/demo --singlejar 9090
Started Demo gRPC Server on localhost at port: 9090
810181 PID written to /tmp/ServerPID

$ ./enola -vvv get --model file:docs/use/connector/model-grpc.yaml demo.book_kind/0-13-140731-7
2023-05-24 22:56:51 WARNING io.grpc.NameResolverRegistry getDefaultRegistry No NameResolverProviders found via ServiceLoader, including for DNS. This is probably due to a broken build. If using ProGuard, check your configuration
io.grpc.ManagedChannelRegistry$ProviderNotFoundException: No functional channel service provider found. Try adding a dependency on the grpc-okhttp, grpc-netty, or grpc-netty-shaded artifact
        at io.grpc.ManagedChannelRegistry.newChannelBuilder(ManagedChannelRegistry.java:181)
        at io.grpc.ManagedChannelRegistry.newChannelBuilder(ManagedChannelRegistry.java:157)
        at io.grpc.Grpc.newChannelBuilder(Grpc.java:101)
        at dev.enola.core.aspects.GrpcAspect.<init>(GrpcAspect.java:42)
        at dev.enola.core.EnolaServiceProvider.get(EnolaServiceProvider.java:72)
        at dev.enola.cli.CommandWithEntityID.run(CommandWithEntityID.java:38)

The reason for this was subtle, and took me a moment to figure out... 😄 It was that the @maven//:io_grpc_grpc_netty really needs to be a runtime_deps not just of java_test but of the java_library(name = "impl" in core/impl/BUILD.

It's bad that ./test.bash does not detect that - I'll try to fix both the missing test coverage and actual problem.

Wehl... this is a very special corner case that's difficult to cover - not worth it.

The Executable Markdown / Demo does find it anyway (as has happened here).

[vorburger]

@maven//:io_grpc_grpc_netty really needs to be

a runtime_deps of BOTH java_test AND java_library in core/impl/BUILD AS WELL AS connectors/demo/BUILD, to fix:

io.grpc.ManagedChannelProvider$ProviderNotFoundException: No functional server found. Try adding a dependency on the grpc-netty or grpc-netty-shaded artifact
        at io.grpc.ServerProvider.provider(ServerProvider.java:44)
        at io.grpc.ServerBuilder.forPort(ServerBuilder.java:44)
        at dev.enola.demo.Server.start(Server.java:44)
        at dev.enola.demo.ServerTest.testServer(ServerTest.java:37)