Join Slack
Powered by
Running in IDEA but not Gradle for has typically i...
# test
t
tddmonkey
12/09/2018, 10:24 AM
Running in IDEA but not Gradle for has typically indicated a dependency issue. IDEA flattens them out so you can’t spot them there. Have you got something in the wrong scope? Or accidentally relying on something transient in the wrong scope?
3
Views
Open in Slack
Previous
Next