Proto resolution mess up

[leozc]

Proto resolution mess up

[benjyw]

This is because the Python protobuf plugin is inferring a dependency from the protobuf_sources target to the protobuf distribution, and then the Java backend is trying to build a classpath entry out of this, and obviously cannot.

As a workaround you can turn the dep inference off with

[python-protobuf]
infer_runtime_dependency = false

in pants.toml. But then your Python side may not work, and you'll have to manually add back that dep from the relevant python_sources so it gets pulled in. Again, this is just a workaround until I figure out something more robust.

[benjyw]

@leozc can you add some python code that uses the python-generated protobuf code (generated from the same Event.proto) to the example repo? I'd like to see more closely how those interact.

[leozc]

will do

[benjyw]

@leozc best to @ me here and/or on Slack when this is ready, thanks!