Package conflicts exist between proto and non-proto modules.
See original GitHub issueJava classes that are currently generated from Protobuf definitions have overlapping package names with Feast modules. This causes conflicts when trying to import classes from Feast modules.
For example the CoreService.proto uses feast.core
, which is also in use by the Feast Core
module: example.
Proposal is to prefix all proto generated packages with .proto
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Package conflicts exist between proto and non-proto modules.
Java classes that are currently generated from Protobuf definitions have overlapping package names with Feast modules. This causes conflicts ...
Read more >Package conflicts with automatic modules in Java 9
So my questions are: Am I using the new module system correctly? What can I do about this error? and; Do these dependencies...
Read more >Upgrading OL7 > OL8 Leapp package conflict — oracle-tech
Hello all, I'm attempting to upgrade from OL 7 to 8 using leapp.
Read more >Package conflicts - Unity - Manual
A conflict exists when a Project has dependencies on a package with different versions. A conflict can only exist between two indirect dependencies, ......
Read more >Packaging:Conflicts - Fedora Project Wiki
Common Conflicting Files Cases and Solutions. There are many types of files which can conflict between multiple packages. Fedora strongly ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
BTW, I’m not going to lose sleep over this so don’t let me block you.
I’m not so opinionated about this, so you guys go ahead. I prefer
proto
towire
though, as it is more meaningful.