search

GoogleCloudPlatform / gradle-appengine-plugin

Gradle plugin that provides tasks for uploading, running and managing Google App Engine projects
Apache License 2.0
236 stars 60 forks source link

Warning messages when using Gradle 4.0 #290

Open jiakuan opened 7 years ago

jiakuan commented 7 years ago

After I upgraded to Gradle 4.0, I saw the following warning messages which might be something need to be aware of.

The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead.
Gradle now uses separate output directories for each JVM language, but this build assumes a single directory for all classes from a source set. This behaviour has been deprecated and is scheduled to be removed in Gradle 5.0
        at build_32bapygwgn43ck9xwcttab0k9.run(/Users/jake/work/my-app/build.gradle:35)
The setTestClassesDir(File) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use the setTestClassesDirs(FileCollection) method instead.
        at build_32bapygwgn43ck9xwcttab0k9.run(/Users/jake/work/my-app/build.gradle:35)

The line 35 of my build file is this:

apply plugin: 'appengine'
loosebazooka commented 7 years ago

Yeah it's probably cause we use << somewhere in the code.

On Jul 1, 2017 02:31, "Jake W" notifications@github.com wrote:

After I upgraded to Gradle 4.0, I saw the following warning messages which might be something to be aware of.

The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. Gradle now uses separate output directories for each JVM language, but this build assumes a single directory for all classes from a source set. This behaviour has been deprecated and is scheduled to be removed in Gradle 5.0 at build_32bapygwgn43ck9xwcttab0k9.run(/Users/jake/work/my-app/build.gradle:35) The setTestClassesDir(File) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use the setTestClassesDirs(FileCollection) method instead. at build_32bapygwgn43ck9xwcttab0k9.run(/Users/jake/work/my-app/build.gradle:35)

The line 35 of my build file is this:

apply plugin: 'appengine'

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GoogleCloudPlatform/gradle-appengine-plugin/issues/290, or mute the thread https://github.com/notifications/unsubscribe-auth/ABPo-sLn082RXaECgmuXYSIaohOWNHIZks5sJfXrgaJpZM4OLPtP .

loosebazooka commented 7 years ago

It's safe to ignore for now, I'll try to fix it in the next release.

On Jul 1, 2017 08:00, "Appu Goundan" appu@google.com wrote:

Yeah it's probably cause we use << somewhere in the code.

On Jul 1, 2017 02:31, "Jake W" notifications@github.com wrote:

After I upgraded to Gradle 4.0, I saw the following warning messages which might be something to be aware of.

The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. Gradle now uses separate output directories for each JVM language, but this build assumes a single directory for all classes from a source set. This behaviour has been deprecated and is scheduled to be removed in Gradle 5.0 at build_32bapygwgn43ck9xwcttab0k9.run(/Users/jake/work/my-app/build.gradle:35) The setTestClassesDir(File) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use the setTestClassesDirs(FileCollection) method instead. at build_32bapygwgn43ck9xwcttab0k9.run(/Users/jake/work/my-app/build.gradle:35)

The line 35 of my build file is this:

apply plugin: 'appengine'

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GoogleCloudPlatform/gradle-appengine-plugin/issues/290, or mute the thread https://github.com/notifications/unsubscribe-auth/ABPo-sLn082RXaECgmuXYSIaohOWNHIZks5sJfXrgaJpZM4OLPtP .

loosebazooka commented 7 years ago

Pull requests are also appreciated

On Jul 1, 2017 08:01, "Appu Goundan" appu@google.com wrote:

It's safe to ignore for now, I'll try to fix it in the next release.

On Jul 1, 2017 08:00, "Appu Goundan" appu@google.com wrote:

Yeah it's probably cause we use << somewhere in the code.

On Jul 1, 2017 02:31, "Jake W" notifications@github.com wrote:

After I upgraded to Gradle 4.0, I saw the following warning messages which might be something to be aware of.

The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. Gradle now uses separate output directories for each JVM language, but this build assumes a single directory for all classes from a source set. This behaviour has been deprecated and is scheduled to be removed in Gradle 5.0 at build_32bapygwgn43ck9xwcttab0k9.run(/Users/jake/work/my-app/build.gradle:35) The setTestClassesDir(File) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use the setTestClassesDirs(FileCollection) method instead. at build_32bapygwgn43ck9xwcttab0k9.run(/Users/jake/work/my-app/build.gradle:35)

The line 35 of my build file is this:

apply plugin: 'appengine'

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GoogleCloudPlatform/gradle-appengine-plugin/issues/290, or mute the thread https://github.com/notifications/unsubscribe-auth/ABPo-sLn082RXaECgmuXYSIaohOWNHIZks5sJfXrgaJpZM4OLPtP .

loosebazooka commented 7 years ago

I actually misread this whole thing. It's a different issue than I though but still a method deprecation issue.. I'll keep it open.

jkrez commented 6 years ago

One of the issues is using setTestClassesDir -> which is deprecated: https://github.com/GoogleCloudPlatform/gradle-appengine-plugin/blob/master/src/main/groovy/com/google/appengine/AppEnginePlugin.groovy#L666

Instead the recommendation is to use setTestClassesDirs with a file collection

patflynn commented 6 years ago

Just a reminder to everyone that this plugin is deprecated. No further maintenance is planned and you're encouraged to start using our new cloud sdk based plugin which you can find here.