Scalapb.proto would result in a name clash for clearExtension method in OneofOptionsBuilder about scalapb HOT 8 CLOSED

Can you provide step-by-step instructions on how to reproduce the problem you are seeing?

from scalapb.

I've setup a small sample project here: https://github.com/shikai93/scalapb-test
I hope thats helpful ~
It only contains the scalapb.proto and google well-known protos.

from scalapb.

Can you include the project directory and build.sbt files? Is it possible that you are trying to generate Scala or Java code for protos in protos/google/protobuf which already have classes generated for?

from scalapb.

It looks like it is generating code for messages that are already included with protobuf-java here: https://github.com/shikai93/scalapb-test/blob/24c0e187c5d9aa9e1ea15eb78d792c85d7bab630/scala/project/Settings.scala#L18

They can be made available by adding:

libraryDependencies += "com.thesamet.scalapb" %% "scalapb-runtime" % scalapb.compiler.Version.scalapbVersion % "protobuf"

from scalapb.

they are actually within the scala folder, let me pull them up one level.

you are right that i am trying to generate the messages already included. But i did not integrate in the relevant dependencies for common-proto
libraryDependencies ++= Seq( "com.thesamet.scalapb.common-protos" %% "proto-google-common-protos-scalapb_0.11" % "2.9.6-0" % "protobuf", "com.thesamet.scalapb.common-protos" %% "proto-google-common-protos-scalapb_0.11" % "2.9.6-0" )
so i was under the impression that this clash would not occur

from scalapb.

But i did not integrate in the relevant dependencies for common-proto

The one causing the problem are the one in google/protobuf which are included in scalapb-runtime for Scala and protobuf-java for Java.

from scalapb.

I see, i think this was a change induced in 0.11.14?
But yes, changing them to includePath worked for my case, updated my test case repo, thanks for the help! I shall close this issue

from scalapb.

The error seems to appear in the Java generated code, maybe there's a bump in the protoc version somewhere in your toolchain that triggered it, but it's odd that this set up ever worked.

from scalapb.