

The benefit of this mapping is that we no longer use `minus` configurations, which we might wantįacing the same problem with Android Studio 3.3.1

`TEST`= `testCompileClasspath + testRuntimeClasspath` The default mapping for the Java plugin is simplified to: those scopes are not postprocessed in any way the IdeaPlugin uses the same API for adding dependencies that the user would use users can put dependencies into the 4 IDEA scopes (`COMPILE`,`PROVIDED`,`RUNTIME`, `TEST`)

no hardcoded mapping rules for the Java plugin The new implementation accepts IDEA's dependency model and does the simples possible mapping to it: In auto completion, it is hard to follow, as IDEA itself simply does not differentiate between While this slightly reduces the number of false positives Remove `testRuntime` dependencies from the `TEST` scope if they were already in the `RUNTIME` Mapping in an attempt to minimize the number of dependency declarations in IDEA, e.g. The old scope mapping code was hardcoded, hard to understand and exploded in complexityĮach time we added a new configuration to the Java plugin.
