flasn4nt
/
grpc-java
mirror of https://github.com/grpc/grpc-java.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
grpc-java/protobuf/build.gradle

42 lines
1.1 KiB
Groovy
Raw Normal View History

Swap to Gradle's Plugin DSL for much of build Examples and android projects were left unchanged. They can be changed later. No plugin versions were changed, to make this as non-functional of a change as possible. Upgrading Gradle to 5.6 was necessary for pluginManagement in settings.gradle.
2019-09-07 23:18:57 +08:00
plugins {
all: migrate gradle build to java-library plugin - Use gradle configuration `api` for dependencies that are part of grpc public api signatures. - Replace deprecated gradle configurations `compile`, `testCompile`, `runtime` and `testRuntime`. - With minimal change in dependencies: If we need dep X and Y to compile our code, and if X transitively depends on Y, then our build would still pass even if we only include X as `compile`/`implementation` dependency for our project. Ideally we should include both X and Y explicitly as `implementation` dependency for our project, but in this PR we don't add the missing Y if it is previously missing.
2020-05-05 07:44:30 +08:00
id "java-library"
Apply maven-publish plugin explicitly when needed
2019-09-08 00:27:32 +08:00
id "maven-publish"
Swap to Gradle's Plugin DSL for much of build Examples and android projects were left unchanged. They can be changed later. No plugin versions were changed, to make this as non-functional of a change as possible. Upgrading Gradle to 5.6 was necessary for pluginManagement in settings.gradle.
2019-09-07 23:18:57 +08:00
id "com.google.protobuf"
Apply japicmp plugin explicitly when needed
2019-09-08 01:23:23 +08:00
id "me.champeau.gradle.japicmp"
Apply animalsniffer plugin explicitly when needed
2019-09-08 01:38:58 +08:00
id "ru.vyarus.animalsniffer"
protobuf: utility methods for com.google.rpc.Status
2017-03-22 05:03:46 +08:00
}
Swap to Gradle's Plugin DSL for much of build Examples and android projects were left unchanged. They can be changed later. No plugin versions were changed, to make this as non-functional of a change as possible. Upgrading Gradle to 5.6 was necessary for pluginManagement in settings.gradle.
2019-09-07 23:18:57 +08:00
description = 'gRPC: Protobuf'
all: generate automatic module name in the manifest (#10413)
2023-07-26 00:00:11 +08:00
tasks.named("jar").configure {
manifest {
attributes('Automatic-Module-Name': 'io.grpc.protobuf')
}
}
Split protobuf into its own project We don't want core to depend on protobuf.
2015-04-11 06:40:44 +08:00
dependencies {
all: migrate gradle build to java-library plugin - Use gradle configuration `api` for dependencies that are part of grpc public api signatures. - Replace deprecated gradle configurations `compile`, `testCompile`, `runtime` and `testRuntime`. - With minimal change in dependencies: If we need dep X and Y to compile our code, and if X transitively depends on Y, then our build would still pass even if we only include X as `compile`/`implementation` dependency for our project. Ideally we should include both X and Y explicitly as `implementation` dependency for our project, but in this PR we don't add the missing Y if it is previously missing.
2020-05-05 07:44:30 +08:00
api project(':grpc-api'),
libraries.jsr305,
Use Gradle's version catalog This moves our depedencies into a plain file that can be read and updated by tooling. While the current tooling is not particularly better than just using gradle-versions-plugin, it should put us on better footing. gradle-versions-plugin is actually pretty nice, but will be incompatible with Gradle 8, so we need to wait a bit to see what the future holds. Left libraries as an alias for libs to reduce the commit size and make it easier to revert if we don't end up liking this approach. We're using Gradle 7.3.3 where it was an incubating fetaure. But in Gradle 7.4 is became stable.
2022-06-14 03:09:30 +08:00
libraries.protobuf.java
Replace failOnVersionConflict() with custom requireUpperBoundDeps failOnVersionConflict has never been good for us. It is equivalent to Maven dependencyConvergence which we discourage our users to use because it is too tempermental and _creates_ version skew issues over time. However, we had no real alternative for determining if our deps would be misinterpeted by Maven. failOnVersionConflict has been a constant drain and makes it really hard to do seemingly-trivial upgrades. As evidenced by protobuf/build.gradle in this change, it also caused _us_ to introduce a version downgrade. This introduces our own custom requireUpperBoundDeps implementation so that we can get back to simple dependency upgrades _and_ increase our confidence in a consistent dependency tree.
2021-06-12 05:01:18 +08:00
implementation libraries.guava
Bump to Guava 20 Fixes #4176
2018-03-24 06:45:05 +08:00
Use Gradle's version catalog This moves our depedencies into a plain file that can be read and updated by tooling. While the current tooling is not particularly better than just using gradle-versions-plugin, it should put us on better footing. gradle-versions-plugin is actually pretty nice, but will be incompatible with Gradle 8, so we need to wait a bit to see what the future holds. Left libraries as an alias for libs to reduce the commit size and make it easier to revert if we don't end up liking this approach. We're using Gradle 7.3.3 where it was an incubating fetaure. But in Gradle 7.4 is became stable.
2022-06-14 03:09:30 +08:00
api (libraries.google.api.protos) {
build,protobuf: update google_api_protos dependency
2017-05-02 05:43:53 +08:00
// 'com.google.api:api-common' transitively depends on auto-value, which breaks our
// annotations.
exclude group: 'com.google.api', module: 'api-common'
protobuf: utility methods for com.google.rpc.Status
2017-03-22 05:03:46 +08:00
}
Change many api deps to implementation deps These look pretty fair now, mostly only exposing grpc-api and annotations as api dependencies.
2023-12-16 07:14:29 +08:00
implementation (project(':grpc-protobuf-lite')) {
protobuf: Exclude new javalite artifact name In 48929c4 the protobuf lite artifact name changed from protobuf-lite to protobuf-javalite. However, the exclusion in grpc-protobuf was missed in the update, allowing protobuf lite to leak into the classpath. This restores the previous behavior of only having one protobuf implementation on the classpath.
2019-11-19 11:54:05 +08:00
exclude group: 'com.google.protobuf', module: 'protobuf-javalite'
Begin consuming protobuf-lite artifact Protobuf-lite since beta-4 is now more of a fork than a subset of protobuf-java, which may cause us problems later since lite API is not stable. Also, lite-generated code may now depend on APIs only in protobuf-lite, so our users must depend on the protobuf-lite runtime. Having all our users explicitly override the dependency is bothersome to them and can easily only expose problems only after we do a release. So now we are doing the dependency overriding; most users should "just work" and pick up the correct protobuf artifact. I've confirmed the exclusion is listed in the grpc-protobuf pom and "gradle dependencies" and "mvn dependency:tree" do not include protobuf-lite for the examples. Vanilla protobuf users are most likely to experience any breakage, which should detect problems more quickly since we use protobuf-java more frequently than protobuf-lite during development. protobuf-lite does not include pre-generated code for the well-known protos, so users will need to generate them themselves for the moment (google/protobuf#1889). Note that today changing deps does not noticeably reduce the method code for our users, since ProGuard already is stripping most classes. The difference in output is only a reduction of 3 classes and 6 methods for the android example.
2016-07-30 02:57:41 +08:00
}
Enable Animal Sniffer for protobuf projects This ensures that we remain JDK6/Android-compatible.
2015-08-14 05:39:34 +08:00
Swap Animalsniffer to Java 8 and Android 19 Also added missing signatures. Swapping to version catalog will make this process easier in the future.
2022-08-11 03:41:57 +08:00
signature libraries.signature.java
signature libraries.signature.android
Enable Animal Sniffer for protobuf projects This ensures that we remain JDK6/Android-compatible.
2015-08-14 05:39:34 +08:00
}
Link JavaDoc to protobuf JavaDoc This breaks javanano links, but the value to normal and lite proto seems more important.
2015-08-19 05:04:30 +08:00
Use Gradle's task configuration avoidance APIs This can avoid creating an additional 736 tasks (previously 502 out of 1591 were not created). That's not all that important as the build time is essentially the same, but this lets us see the poor behavior of the protobuf plugin in our own project and increase our understanding of how to avoid task creation when developing the plugin. Of the tasks still being created, protobuf is the highest contributor with 165 tasks, followed by maven-publish with 76 and appengine with 53. The remaining 59 are from our own build, but indirectly caused by maven-publish.
2022-07-02 06:48:38 +08:00
tasks.named("javadoc").configure {
Use Javadoc's -linkoffline instead of -link `-link` does I/O to download the package list, for every javadoc invocation. There is no caching, so this happens many times per build. Swap to offline mode to avoid spamming the servers, and avoid build failures if the servers aren't entirely healthy.
2024-02-24 08:27:18 +08:00
options.linksOffline 'https://protobuf.dev/reference/java/api-docs/',
"${rootProject.projectDir}/gradle/javadoc/protobuf.dev-reference-java-api-docs/"
Use Gradle's task configuration avoidance APIs This can avoid creating an additional 736 tasks (previously 502 out of 1591 were not created). That's not all that important as the build time is essentially the same, but this lets us see the poor behavior of the protobuf plugin in our own project and increase our understanding of how to avoid task creation when developing the plugin. Of the tasks still being created, protobuf is the highest contributor with 165 tasks, followed by maven-publish with 76 and appengine with 53. The remaining 59 are from our own build, but indirectly caused by maven-publish.
2022-07-02 06:48:38 +08:00
}