Configuring Project Fails when non-jar in build classpath #1021
Comments
Thank you for the report @jasongilanfarr! It is definitely very similar to https://youtrack.jetbrains.com/issue/KT-10328 that was fixed with the |
@jasongilanfarr, the stacktrace in your snippet is from a warning log coming from the Kotlin compiler. This warning doesn't fail the build. |
@eskatos That is what I thought too. Unfortunately, our build scans are not public, but here is the full stack trace:
|
Thank you Jason! The issue is in |
Thanks again for the report Jason, this has been fixed in #1039 and will be part of the next release. |
Expected Behavior
Configuring Project should succeed.
Current Behavior
Context
Our build classpath, due to transitive dependencies happens to have a lot of xml, tar.gz, and pom files in it, so when we try to use a kotlin build, we can't get past the configuration step.
It looks like this should be fixed (https://youtrack.jetbrains.com/issue/KT-10328 and https://youtrack.jetbrains.com/issue/KT-17140), but no version of kotlin-dsl, kotlin, and gradle have managed to work.
Steps to Reproduce (for bugs)
Use a plugin (or buildSrc) that has a non-jar file in the classpath.
Your Environment
Unfortunately, I am unable to provide exact details, but here is gradle --version
Gradle 4.10-rc-1
Build time: 2018-08-09 06:19:37 UTC
Revision: 97951b7f541f1da43de291246cc7b17507e75a14
Kotlin DSL: 1.0-rc-1
Kotlin: 1.2.60
Groovy: 2.4.15
Ant: Apache Ant(TM) version 1.9.11 compiled on March 23 2018
JVM: 1.8.0_121 (Oracle Corporation 25.121-b13)
OS: Linux 3.10.0-514.36.5.el7.x86_64 amd64
Note that I tried 4.8, 4.9, and 4.10-rc-1 as well as attempting to try other version combinations.
The text was updated successfully, but these errors were encountered: