2020a protobuf version
24 vues (au cours des 30 derniers jours)
A few years ago I wrote some hybrid Java/Matlab code to handle reading/writing Google protobuf messages. Initially I built this on protobuf version 3.5.0. More recently I updated this code to use protobuf version 3.7.1. This code no longer works after updating to Matlab 2020a when using the .jar's I compiled with protobuf 3.7.1; it still works with the .jar's using 3.5.0. I came across a forum here that leads me to believe the issue is that Matlab is now shipping with "built in" protobuf jars (R2020A\java\jarext\protobuf3.jar), which it adds to its static Java path, but conflict with certain newer protobuf features. Because it is on the static path I can't dynamically give my jars "preference" via javaaddpath. The only work-around I can think of is via a javaclasspath file to update the static path, but this is not a reasonable option as the code is used by multiple users on different machines via a network license. Is there anything I can do about this? It's been quite a while, but I believe I moved from protobuf version 3.5.0 up to 3.7.1 because the older one can conflict with some features in newer Java versions, so it's unstable in more recent versions of Matlab. Which protobuf versions are supported by the protobuf3.jar included with R2020a? If it supports protobuf 3.6.x I can try compiling my code again using that version, assuming it is supported by newer Java versions. Thanks!