Open eyJhb opened 4 years ago
Seems this is fixed, by cleaning the cache
rm -rf ~/.gradle
rm -rf .gradle
Going to reopen this again, as it did not fix the issue for me, I still think this may be the main blocker. Because Android does not provide defaults.. Sadly.
A way this might get fixed/better, is that instead of a project we allow for the ability to specify a task/list of tasks that we want the dependencies for. Because I think it is AntennaPod that has a weird task some place, that is just legacy
I'll look into it, but I don't think it will be possible get all of the required dependency configurations given a task. Gradle itself doesn't enforce that configurations are part of task inputs, and tasks can run arbitrary code to resolve whatever configurations they like.
An interesting idea is to duplicate the code used for dependency locking in later gradle versions, where we run a task and scan for resolved configurations after the fact. I'm not sure if this will be universally possible, however.
If you're feeling adventurous, you might try specifying configurations manually with the "--configuration/-c" flag, one per configuration. This will be annoying for Android in particular as it adds a ton of configurations; use ./gradlew :$project:dependencies
to get a full list.
It would be nice to get a pr. task dependency list. I have tried playing a little with the other, but didn't seem to work great... Tried for a few hours to get it to work, but atm. I guess I have to accept some applications not working.
Is there maybe a way, we can use the Gradle cache to get all the dependencies, and then parse that?
E.g. I will rm -rf ~/.gradle
before I run a task, and then parse the ~/.gradle
dir after, and all the files in there must be the dependencies?
I have tried the lenient config branch, and it seems to work well. There is one issue however.
When I use it on antennapod Android app source, I get these errors
Which seems like the thing in https://github.com/gradle/gradle/issues/5953
But I have no skills in this what so ever, hoping @tadfisher might know a trick to get this running. Seems like the last thing, before we can get Android apps build.