-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Classpath container include 'build/main' entries when using Kotlin 1.8.20 #1238
Comments
The
|
Thanks @donat! This commit did the trick for us spring-projects/spring-boot@13d00d8 |
@donat I think we have a similar problem with Spring Boot's Gradle Plugin for ahead-of-time processing. Is this something that you can fix in Buildship? My expectation was that it would "deduplicate" |
See also #1236 (probably would be fixed the same way - de-deuplication of classpath entries). |
Kotlin 1.9.0 will restore the behaviour in 1.8.10 |
Unfortunately, we detected that reverting the behaviour back to 1.8.10 clashes with a workaround applied for: Which relates to gradle/gradle#23932 I therefore need to revoke the previous message. We are aiming to restore behaviour in 1.9, but the first attempt failed and the initial beta is right around the corner already. cc @Tapchicoma |
AIUI, the NBT Gradle Plugin also configures things in such a way that |
For now, the change in KGP was reverted and will likely be shipped in 1.9.0-Beta |
Expected Behavior
When importing a project that has the Kotlin Gradle plugin the eclipse classpath should not include entries for the
build/classes/java
andbuild/classes/kotlin
. Having these additional entries makes Eclipse hard to use. For example, searching for a type will find both the source code and the previously built.class
file.Current Behavior
When using Kotlin 1.8.20 additional classpath entries are added. Downgrading to Kotlin 1.8.10 fixes the issue.
Context
Originally discovered in spring-projects/spring-boot#35101
Steps to Reproduce
https://github.com/philwebb/kotlin-buildship-classpath-bug
Your Environment
Details are in the reproducer project readme
The text was updated successfully, but these errors were encountered: