-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle task not found #1243
Comments
do the |
Just tried out all 6 tasks listed, all report task not found |
thats....really confusing. Maybe related to kotlin gradle script stuff. Have you tried running the task from IDE instead of command line? Curious if that says anything different |
Tasks are all listed in the Gradle panel (Android Studio) |
yea and their appearance in the list should mean the tasks are actually working... what version of gradle are you using? |
Just migrated backed to a groovy script, same issue
My gradle version is 5.2.1 |
it might be a gradle compatibility issue. I'll try upgrading our test suite to 5.2.1 and see what happens |
I'll try to downgrade to 4.10.2, good luck |
^
In case you need the current project that produces this issue, I thought it would be helpful My local development has more few commits ahead with the master branch, but you can pretty much start from there. |
thanks for linking the project, will be easier to debug from that |
do you mind pushing a branch with everything in groovy/gradle4.10.2? will be a bit easier from my end |
Done, haven't thought of that, thank for the suggestion |
yup i see it too. Very weird bug. The only thing I can think of is that it still has to do with the gradle kotlin dsl since the root project uses it. We'll have to setup a test case in repo for the kotlin dsl to make sure it works |
Same issue here, reverted to 1.0.3 fttb. |
I believe this is due to enabling configure on demand in Gradle which somehow breaks the SQLDelight plugin. |
@ansman did the latest release fix this? |
Hi, info on when this issue will be fixed? Thanks |
its caused by enabling configure on demand |
did you mean this? org.gradle.configureondemand=false |
Any known solutions? |
@ATizik make sure you don’t have it in Perhaps SQLDelight should throw an error when CoD is detected until it’s been fixed. |
@ansman |
@ATizik Just had the same problem. I was trying to run the gradleTask via IntelliJ. I had to go into the IntelliJ Preferences -> Build, Execution, Deployment -> Gradle-Android Compiler and disable Configure On Demand. |
@kgonyon |
turns out this is actually preventing us from upgrading the sample to 1.1.3 because we use configure on demand for CI, so this is pretty high priority I'm going to need to rethink the sqldelight gradle lifecycle more. It's too late to rework things right now but here's what I think needs to be done: Right now we rely on That's pretty hacky regardless, so probably what we need to do is use task creation callbacks instead of project evaluation callbacks. The original problem was that kotlin multiplatform adds the android compilation tasks late in gradles lifecycle, and There's also some implications for multi-module here, since module properties are initialized during |
Hi all, Are there good news? Thanks |
|
@AlecStrong was this fixed? I'm having a similar issue in my project (although I'm not using SqlDelight), can you let me know how you fixed this? Cheers. |
It's fixed on master, but theres a bug I'm trying to work through before
doing a release. You can try using the snapshot version
…On Sat., Jul. 6, 2019, 5:18 a.m. Franco Sabadini, ***@***.***> wrote:
@AlecStrong <https://github.com/AlecStrong> was this fixed? I'm having a
similar issue in my project (although I'm not using SqlDelight), can you
let me know how you fixed this? Cheers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1243>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMZBQFSDLAHOD54WR5SXSDP6BPNTANCNFSM4G2W5W3A>
.
|
The fix was to not rely on the gradle.projectsEvaluated api
…On Sat., Jul. 6, 2019, 9:06 a.m. Alec Strong, ***@***.***> wrote:
It's fixed on master, but theres a bug I'm trying to work through before
doing a release. You can try using the snapshot version
On Sat., Jul. 6, 2019, 5:18 a.m. Franco Sabadini, <
***@***.***> wrote:
> @AlecStrong <https://github.com/AlecStrong> was this fixed? I'm having a
> similar issue in my project (although I'm not using SqlDelight), can you
> let me know how you fixed this? Cheers.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1243>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAMZBQFSDLAHOD54WR5SXSDP6BPNTANCNFSM4G2W5W3A>
> .
>
|
Component: sqldelight-gradle-plugin
Version: both 1.1.0-SNAPSHOT and 1.2.0-SNAPSHOT
Configuration:
build.gradle.kts (common)
sqldelight.gradle (common)
Step to reproduce:
gradlew common:tasks
gradlew common:generateMetadataMainTodoSqlDelightDatabaseInterface
The text was updated successfully, but these errors were encountered: