Open vicmosin opened 3 years ago
Is there any progress on this issue?
Yes, optimizeCodegen=true
seems to be a workaround, but I don't think it should be accepted as a solution.
Not sure it'll move forward without some support for the project
hi, im facing the same error.... some solutions? or where do you put optimizeCodegen=true option?
This is #121, #60, #117.
The error manifests because of an interplay between <includeStdTypes>
, <protocArtifact>
, and <protocVersion>
.
<includeStdTypes>
triggers a protocol major version lookup<protocVersion>
is set and otherwise sets local6=null
<protocArtifact>
usually takes the place of <protocVersion>
because of #139 (#61).Fortunately <protocArtifact>
supersedes <protocVersion>
for protoc
resolution so all three settings can be safely specified.
Alternatively, it may be that <includeMavenTypes>
can safely and adequately substitute <includeStdTypes>
and thereby obviate <protocVersion>
. I have not tried this.
mvn clean
mvn generate-sources
-> generates initiallymvn generate-sources
-> fails withConfig to reproduce:
I assume that happens only when
optimizeCodegen=true
, setting it to false works (at least as workaround)