Both locally and on our CI build

And this morning not anymore

It may be in cache somewhere in our infra

Not sure why

But I wanted to check with you that not other new build has been published

well, the main 1.1-beta-17 build released to Maven Central is technically another build, but it’s equivalent to the one that was republished to Bintray 2 days ago. And we only did republish the Bintray build once

Are you 100% sure that the 1.1-beta-17 on Maven Central really include the fix you put in the version published on Bintray ???

Because that could explain our issue

Yesterday no artificat on Maven Central and our project was fine

Today it finally hit Maven Central

let me check

sorry, there’s no 1.1.0-beta-17 on Maven Central, I was slightly confused myself… Since it’s an EAP, the build is released on the kotlin-eap-1.1 Bintray channel. Let me check that one

Ok

Based on my test we have the wrong version in cache on our Artifactory

Not sure why

So I guess bintray version on ok

(would be nice to bump the version next time if you can)

I’ve checked the 1.1.0-beta-17 in kotlin-eap-1.1, it works fine

Ok

So we have the old in cache

Not sure how it went there

We are going to cleanup the cache and all

.gradle/cache

locally

(would be nice to bump the version next time if you can)

Yes, sorry for that — I figured it’s OK to republish the kotlin-dev version (because it’s dev), not knowing that the same version will be used for the final build

Thanks for your help

Yes for dev that was ok

I was surprised to see it was the final

It seems that calling

hashCode()

on a top level function reference results in a NullPointerException in 1.1.0-beta-17 From what I can tell it's because

getOwner()

is null in

kotlin.jvm.internal.FunctionReference

for top level functions is this a known issue or should I open a ticket on YouTrack?

@viorgu do you have a dependency on kotlin-reflect?

in any case, please report

no dependency on reflect, only on the stdlib, should I try with the reflect lib as well?