ProtocPlugin should not activate for all projects in a multi-project build
See original GitHub issueoverride def trigger: PluginTrigger = allRequirements
should be replaced with
override def trigger: PluginTrigger = noTrigger
(or just deleted, as noTrigger
is the default).
projectSettings
has side-effects (e.g., creating directories) and so it should not be called unless the plugin has been explicitly enabled.
(This is especially annoying when using AkkaGrpcPlugin
, which does not auto-activate; but its dependency on ProtocPlugin triggers a project-wide activation.)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Support protoc maven plugin · Issue #230 - GitHub
The original plugin is not maintained. Need to support it again: The original one is: ...
Read more >Protocol Buffer imports not recognized in Intellij - Stack Overflow
If you're using IntelliJ IDEA, go to Preferences -> Protobuf Support and add the path to your .proto file. This would resolve the...
Read more >Executing Multi-Project Builds - Gradle User Manual
To identify the project structure, you can use gradle projects command. As an example, let's use a multi-project build with the following structure:....
Read more >Setup protobuf for Flutter plugin method channel - Medium
This folder will store all the proto files. Define a message type in employee.proto syntax = "proto3";option java_package = "com.abc.
Read more >Maven Protocol Buffers Plugin – protobuf:compile - Xolstice
It also searches dependency artifacts for .proto files and includes them in the proto_path so that they can be referenced. Finally, it adds...
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 FreeTop 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
Top GitHub Comments
I believe the issue is resolved at this point. Don’t hesitate to leave further comments if there are any undesirable side effects for projects without
PB.targets
I come here with the same problem. I can confirm 1.0.0-RC4 doesn’t have this issue 👍
Thanks Samet