| Age | Commit message (Collapse) | Author |
|---|
|
This opens up the ability of dependency locking and the now-stable Maven
Publish Plugin. Also failOnVersionConflict no longer needs to be
commented out for the dependency insight report.
|
|
The new jmh plugin fixes a warning for the newer version of Gradle.
The new AppEngine plugin still produces a warning, but updating it
anyway so people know that upgrading the plugin doesn't fix the problem.
The new android-maven plugin fixes a build problem with the newer
Gradle.
The Visual Studio fixes were necessary starting ~4.4.
https://github.com/gradle/gradle-native/issues/34#issuecomment-335222096
describes the change in behavior.
There's nothing immediately being used as part of this update. It's just
to keep us current and to get us over that Visual Studio change hump.
|
|
|
|
While this fixes a Gradle-caused failure on Java 9, it is still failing
due to Generated annotations as seen in #3633.
Fixes #3632
|
|
There is a deadlock in 4.0.0 with running tests in parallel
|
|
|
|
|
|
Among build speed improvements and VS 2015 support, it also improves
quote handling in gradlew.
|
|
* all: update to gradle 3.2
|
|
Is faster and includes a security fix.
|
|
This improves our documentation for the gradle protobuf plugin, as its
version is dependent on the gradle version.
Gradle now has the --tests flag, performance improvements, and support
for OpenPGP subkeys.
|
|
|
|
Gets us past some minor DSL changes and should get increased build
performance. Will make it easier to update to 2.11 and other future
versions.
|
|
This fixes a problem where gradle would try to use VC's amd64_x86 cl
(without the correct environment) and fail to compile with return code
-1073741515 (STATU_DLL_NOT_FOUND) because of missing mspdb120.dll.
|
|
|
|
|
|
|
|
|
|
|
