Kyle Moore

Is this a duplicate of #693 ?

Test failures _might_ be due to JDK version discrepancies; travis uses [1.8.0_151](https://travis-ci.com/github/linkedin/rest.li/builds/220952632#L434), while I have 1.8.0_181 locally. I will investigate.

This might be too late. I'm trying to invoke this test locally: `com.linkedin.pegasus.gradle.PegasusPluginIntegrationTest#mainCopySchema task will remove stale pdsc` And it is failing with 500s: ``` Output: > Task :generateDataTemplate FAILED...

It turns out this was an outage with jcenter: https://status.bintray.com/incidents/9n84kbm0bjh0

> is there a company wide initiative to move everyone to gradle>5.4, IMO only removing some warnings by using @Replacedby doesn't fit as a good use-case to do an incompatible...

> > This makes the changes backward-compatible and buys some time, but at some point this plugin will have to use APIs which won't support older versions of Gradle. >...

> IncrementalTaskInputs seems to be deprecated with 6.1 can you find a replacement, rest lgtm Thanks Aman. Yes, that deprecation is addressed by #567 (upon which this PR depends).

@shanman190 I like the `mvnd` option also ([docs](https://github.com/apache/maven-mvnd)). I didn't realize that it's a native executable, which is great. That leads me to another idea for a recipe: adding [Java...

> Let's spin off Java toolchains for Maven to a separate issue. If you're up for providing the features for one or both of them, we can always help on...

My organization sees the following issue when building with 5.6.4:  I would prefer wrapping `JavaScriptMinify` line 44 with a version compatibility check. In pseudocode: ``` if (project.gradleVersion