You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of platform enabling protobuf definitions for gossip events, the package usage was cleaned up to match protobuf recommendations.
This caused pbj-integration-tests to fail because the test compiles both PBJ and protoc and assumes the packages will not match.
The result is a duplicate class error during compilation.
Steps to reproduce
Add platform to pbj-integration-tests as detailed in issue number 241.
Run a gradle build of pbj-integration-tests after setting the protobuf git package to 12473-gossiped-events.
The build should succeed without errors. One possible solution would be to prefix the packages for pbj with pbj when compiling for the integration test only (would require an option to insert a package prefix for the compiler). Not sure if that's reasonable, but it's one option.
Description
As part of platform enabling protobuf definitions for gossip events, the package usage was cleaned up to match protobuf recommendations.
This caused pbj-integration-tests to fail because the test compiles both PBJ and protoc and assumes the packages will not match.
The result is a duplicate class error during compilation.
Steps to reproduce
12473-gossiped-events
.Additional context
Partial log:
What should happen
The build should succeed without errors. One possible solution would be to prefix the packages for pbj with
pbj
when compiling for the integration test only (would require an option to insert a package prefix for the compiler). Not sure if that's reasonable, but it's one option.Related Items
proto
files withoutjava_package
directives #218The text was updated successfully, but these errors were encountered: