-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protobuf plugin v0.9.0-0.9.2 fails to apply to a Quarkus project #659
Comments
The reproducer is here: https://github.com/jskillin-idt/google-protobuf-gradle-plugin-issues-659
The stacktrace as promised:
|
Thank you. This is expected behavior for now. In a future will be provider a Keep the issue open so as not to forget. |
In your case the solution looks like creating another gradle module without quarkus but with java+protobuf. |
I agree! I should've said this in the description. :) I believe the correct "workaround" for this issue (which is honestly probably the correct original implementation to begin with) is to put the protobuf in its own project. |
@rougsig Is it possible to create the configuration with name 'native-testCompileOnly' manually? I don't want to create a submodule. Because I don't know the mechanism of the Quakus "quarkus.generate-code.grpc.scan-for-imports" property. |
It seems that I can use quarkus-grpc to generate the proto. But I can't generate the other language like the protobuf-gradle-plugin does. |
You can try, if native-test doesnt contains any proto files it will be easy. Just |
When creating a project with these two plugins applied:
I receive the following error:
It appears to me that Protobuf is expecting a Java project that creates a source set will always have companion source sets with the "compileOnly" and "implementation" suffixes. It's this expectation that appears to cause the issue.
My next comment will have a reproducer and the full stack trace.
While realistically there's not really going to be many legitimate reasons to combine these two plugins, and is honestly a shortcut on my part, nevertheless I thought it revealed a potential deeper issue and worth reporting.
The text was updated successfully, but these errors were encountered: