Gradle 5.0 Depreciated API features #253

tjoneslo · 2018-07-24T13:35:05Z

A problem was found with the configuration of task '<task>'. Registering invalid inputs and outputs via TaskInputs and TaskOutputs methods has been deprecated and is scheduled to be removed in Gradle 5.0
 - Directory '/Users/tjoneslo/Documents/workspace/<project>/.out/extracted-include-protos/main' specified for property '$3' does not exist.

I get this warning using Gradle 4.6 and protobug-gradle-plugin 0.8.6

The text was updated successfully, but these errors were encountered:

zhangkun83 · 2018-07-25T22:52:49Z

Can you provide a demo project for us to easily reproduce this issue?

davidkraus · 2018-11-20T10:16:31Z

same/similar issue:

* What went wrong:
A problem was found with the configuration of task ':app:generateDebugProto'.
> Directory '/Users/admin/LocalProjects/MyApplication/app/build/extracted-include-protos/main' specified for property '$3' does not exist.

Details:

Android Project (com.android.tools.build:gradle:3.4.0-alpha04) with kotlin-android and kotlin-android-extensions plugins
Gradle 5.0-milestone-1

attached a sample project

MyApplication.zip

Zhuinden · 2018-11-28T00:46:11Z

I just wanted to chime in and say we're also getting this warning, and with Gradle 5.0 being released that's a problem.

But I'm not sure how to get more info out of Gradle 😄

bubenheimer · 2018-12-24T04:59:26Z

I am seeing a similar-looking issue with Gradle 5.0 and protobuf-gradle-plugin 0.8.7. It is a build error, not a warning, and it is a blocker for me. I need to upgrade to Gradle 5.0 to upgrade to errorprone-gradle-plugin 0.6 to upgrade to Dagger 2.20. It looks like this issue has been around for a while and I hope it can be prioritized.

Here's my build output; the various directories correspond to Android productFlavors composing a build variant; I don't think there should be separate directories for these, the only directory needed is extracted-include-protos/fastNocheckLocalDebug, and I see that this directory is indeed created, while the others are not:

Some problems were found with the configuration of task ':app_grpcclient:generateFastNocheckLocalDebugProto'.
> Directory '/Users/uli/Developer/Android/production/Rucksack/app_grpcclient/build/extracted-include-protos/main' specified for property '$3' does not exist.
> Directory '/Users/uli/Developer/Android/production/Rucksack/app_grpcclient/build/extracted-include-protos/local' specified for property '$6' does not exist.
> Directory '/Users/uli/Developer/Android/production/Rucksack/app_grpcclient/build/extracted-include-protos/nocheck' specified for property '$9' does not exist.
> Directory '/Users/uli/Developer/Android/production/Rucksack/app_grpcclient/build/extracted-include-protos/fast' specified for property '$12' does not exist.
> Directory '/Users/uli/Developer/Android/production/Rucksack/app_grpcclient/build/extracted-include-protos/fastNocheckLocal' specified for property '$15' does not exist.

zhangkun83 · 2018-12-29T01:05:17Z

Sorry about the slow response. I have just upgraded the build to Gradle 5.0 (#286) and I am working on adding Gradle 5.0 to the tests. While this particular issue is seemingly straightforward to fix, the tests just start to have various failures with the new Gradle version -- probably not due to bugs of the plugin, but due to the way the tests are written and the way dependencies are wired up. It will take some time to clean things up.

xapienz · 2019-01-02T23:07:14Z

Also facing same problem with Gradle 5.0/5.1.
Workaround to unblock this is to manually create those missing dirs (and add creation of directories somewhere into your own build scripts, so it will work in a clean project), and build finishes successfully.

bubenheimer · 2019-01-04T03:25:57Z

Problem persists with Gradle 5.1 and Android Gradle Plugin 3.4.0-alpha10 (latest preview)

zhangkun83 · 2019-01-04T18:35:49Z

The issue is not an compatibility issue, but rather a functionality issue with Android plugin >= 2.5. The error from Gradle just makes it more obvious. #287 should fix it, and you can find explanation about this issue on that PR. Can any of you check it out, install it locally (./gradlew install -x test) and verify that it works in your project?

xapienz · 2019-01-04T23:58:00Z

@zhangkun83 Worked for me, thank you!

gxshao · 2019-01-09T10:06:53Z

Facing the same problem. And the build.gradle was worked in version 4.6. Now, my gradle version is 5.1...Is that compatibility problem?

Directory ' XXX ' specified for property '$3' does not exist.

Zhuinden · 2019-01-09T10:12:17Z

you need to use the protobuf plugin in this PR: #287

gxshao · 2019-01-09T10:21:31Z

@Zhuinden

Thanks for reply.

I decide to use version 4.10.3 finally. But i wanna make sure it's gonna work for NESTED build right?

…dle 3.0 in tests. (#287) - `gradle/wrapper/gradle-wrapper.properties`: the Protobuf plugin is now built with Gradle 5.1 - `ProtobufPlugin.groovy`: fixed a bug where GenerateProtoTask may "include" the wrong directory when running with Android plugin >= 2.5. - The bug: `addGenerateProtoTask()` always use the directory per *sourceSet* as input (original line 328), but with Android plugin >= 2.5, the extract task writes to the directory per *variant* (original line 272), thus they don't match. The GenerateProtoTask ends up using a nonexistent directory as an input. We didn't catch it in tests because the integration tests were only run with Android plugin up to 2.3. However, Gradle produced a warning about missing input directory, which becomes an error on Gradle 5.0 (#253). Adding Gradle 5.1 and Android 3.1.0 to the test reproduces this bug. - The fix refactored the file and moved the assigning of inputs closer to where the extract task is created. This makes sure the input of the generate task matches the output of the extract task. - Updated tests - Added Gradle 5.1/Android 3.1.0 to tests, and removed Gradle 2.14.1 the oldest version on the tested list, raising the minimum supported version to Gradle 3.0. Removed code paths dedicated to Gradle <3.0. - Gradle 3.0/Android 2.2.0 is commented out from the list because of gradle/gradle#8158. I have verified this pair passes the tests if it's the only one in the list, presumably bypassing the Gradle issue.

Zhuinden · 2019-01-16T16:31:29Z

I see that #287 was merged, is there a release scheduled for 0.8.8? ❤️

zhangkun83 · 2019-01-16T21:56:09Z

0.8.8 is now released.

douruanliang · 2019-06-05T14:17:28Z

I have the same problem ,Android studio 3.4.1 gradle 5.1.1 ，proto setup
protoc {
artifact = 'com.google.protobuf:protoc:3.0.0'
}
plugins {
javalite {
artifact = 'com.google.protobuf:protoc-gen-javalite:3.0.0'
}
}
generateProtoTasks {
all().each { task ->
task.builtins {
remove java
}
task.plugins {
javalite { }
}
}
}

Zhuinden · 2019-06-05T14:55:46Z

@douruanliang const val protobuf_gradle_plugin: String = "0.8.8" ?

zhangkun83 added the gradle compatibility label Dec 13, 2018

zhangkun83 mentioned this issue Jan 4, 2019

Fix support with Gradle 5.x/Android 2.5+; add Gradle 5.1 and drop Gradle 3.0 in tests. #287

Merged

zhangkun83 added the bug label Jan 4, 2019

zhangkun83 self-assigned this Jan 4, 2019

zhangkun83 closed this as completed Jan 16, 2019

zhangkun83 mentioned this issue Apr 25, 2019

Directory '/Users/project/app/build/extracted-include-protos/main' specified for property '$3' does not exist. #311

Closed

voidzcy mentioned this issue Jun 10, 2019

Make generateProtoTask resolve file/directory lazily to allow including build time proto #317

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Gradle 5.0 Depreciated API features #253

Gradle 5.0 Depreciated API features #253

tjoneslo commented Jul 24, 2018

zhangkun83 commented Jul 25, 2018

Uh oh!

davidkraus commented Nov 20, 2018

Uh oh!

Zhuinden commented Nov 28, 2018 •

edited

Loading

Uh oh!

bubenheimer commented Dec 24, 2018

Uh oh!

zhangkun83 commented Dec 29, 2018

Uh oh!

xapienz commented Jan 2, 2019

Uh oh!

bubenheimer commented Jan 4, 2019

Uh oh!

zhangkun83 commented Jan 4, 2019

Uh oh!

xapienz commented Jan 4, 2019

Uh oh!

gxshao commented Jan 9, 2019

Uh oh!

Zhuinden commented Jan 9, 2019

Uh oh!

gxshao commented Jan 9, 2019 •

edited

Loading

Uh oh!

Zhuinden commented Jan 16, 2019

Uh oh!

zhangkun83 commented Jan 16, 2019

Uh oh!

douruanliang commented Jun 5, 2019

Uh oh!

Zhuinden commented Jun 5, 2019

Uh oh!

Gradle 5.0 Depreciated API features #253

Gradle 5.0 Depreciated API features #253

Comments

tjoneslo commented Jul 24, 2018

zhangkun83 commented Jul 25, 2018

Uh oh!

davidkraus commented Nov 20, 2018

Uh oh!

Zhuinden commented Nov 28, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bubenheimer commented Dec 24, 2018

Uh oh!

zhangkun83 commented Dec 29, 2018

Uh oh!

xapienz commented Jan 2, 2019

Uh oh!

bubenheimer commented Jan 4, 2019

Uh oh!

zhangkun83 commented Jan 4, 2019

Uh oh!

xapienz commented Jan 4, 2019

Uh oh!

gxshao commented Jan 9, 2019

Uh oh!

Zhuinden commented Jan 9, 2019

Uh oh!

gxshao commented Jan 9, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Zhuinden commented Jan 16, 2019

Uh oh!

zhangkun83 commented Jan 16, 2019

Uh oh!

douruanliang commented Jun 5, 2019

Uh oh!

Zhuinden commented Jun 5, 2019

Uh oh!

Zhuinden commented Nov 28, 2018 •

edited

Loading

gxshao commented Jan 9, 2019 •

edited

Loading