Dependency scope is 'provided' instead of 'compiled'

Answered

Hello, I have an issue with a gradle project that I have, which didn't exist in an earlier version of IDEA - some of the dependencies are marked as 'Provided' instead of 'Compiled', meaning they don't get included in the classpath in runtime and fail to launch.

I've found that this is a known bug (https://github.com/gradle/gradle/issues/1276) which has since been closed and was tracked down to the "Create module per source set" checkbox. I have that checkbox disabled, and it was disabled during import. I then found the exact same issue on Stack Overflow: https://stackoverflow.com/questions/42443310/why-intellij-idea-dependency-scope-is-provided-instead-of-compile where the person says:

"It's a known issue in IntelliJ IDEA that is specific to Gradle 3.4" ... "You can use Gradle 3.3 or older as a workaround until IDEA 2017.1 is released."

I am using neither Gradle 3.4 (but a local install of Gradle 4.0.2), and 2017.1 has been released as well (I am on 2017.2.1)

Is the bug then still present (doesn't sound like it) or am I doing something wrong?

Thanks!

0
1 comment

There is another open issue which may cause this, see https://youtrack.jetbrains.com/issue/IDEA-170058.

0

Please sign in to leave a comment.