-
-
Notifications
You must be signed in to change notification settings - Fork 779
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
Kotlin 1.3.60 with fix for "Unable to load JNA library" warning #2129
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2129 +/- ##
============================================
- Coverage 80.55% 80.48% -0.07%
Complexity 2016 2016
============================================
Files 336 336
Lines 5802 5802
Branches 1057 1063 +6
============================================
- Hits 4674 4670 -4
Misses 564 564
- Partials 564 568 +4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for investigating this!
* Update KotlinEnvironmentUtils.kt * Kotlin 1.3.60 * Kotlin 1.3.60 * Update KotlinEnvironmentUtils.kt
…kt#2129) * Update KotlinEnvironmentUtils.kt * Kotlin 1.3.60 * Kotlin 1.3.60 * Update KotlinEnvironmentUtils.kt
…kt#2129) * Update KotlinEnvironmentUtils.kt * Kotlin 1.3.60 * Kotlin 1.3.60 * Update KotlinEnvironmentUtils.kt
Update to 1.3.60 which also fixes #2118
As mentioned in JetBrains/kotlin@2568804 by enabling NIO2 in the Kotlin compiler environment it will not attempt to use JNA libraries, avoiding the warning raised in #2118.
This also changes what detekt does to call the function in the Kotlin compiler instead of applying fallback config function in the Kotlin compiler. It's assumed that function will be kept up to date with any necessary fixes/workarounds in future, and also would have avoided the JNA lib warning in the first place.