JavaGradleWorkflow fails with Gradle <3.5; Cannot convert the provided notation to a File or URI about aws-lambda-builders HOT 4 CLOSED

To help understand background on this, is there a reason you cannot use a newer version of Gradle?

from aws-lambda-builders.

A particularly good reason? No. The reality is that the project I first encountered this in is one that hasn’t had updates of any kind in a few years and updating to a modern version of Gradle would require enough changes, between new syntax, plugin updates, and so on, that it isn’t trivial.

from aws-lambda-builders.

I won’t be upset if you close this as “won’t fix”. It’s an old enough version that it would be reasonable to decide not to invest in supporting it.

from aws-lambda-builders.

Hi @davidmc24 ,

I've checked Gradle's plan for marking any release as EOL. And they mention that, once a new release comes out, the older one is marked as EOL.

After a final release, the Gradle team may create additional patch releases that are intended to replace the previous final release due to an important bugfix or regression. For instance, Gradle 5.2.1 replaces the Gradle 5.2 release. Once a release candidate has been made, all feature development moves on to the next release. As such, each Gradle release causes the previous release to become end-of-line (EOL) and that release will not receive any new bugfixes or feature backports.

https://docs.gradle.org/current/userguide/feature_lifecycle.html#eol_support

For that reason, I am going to resolve this issue for now. Please let us know if we can improve anything else for java/gradle workflows.

from aws-lambda-builders.