< msink> I followed your instructions and migrated from bint kotlinlang #multiplatform

@msink I followed your instructions and migrated from bintray to a regular maven-publish plugin. Mostly it works, but there are two problems: • For some reason Bintray treats platform directories as versions and creates versions with names like

dataforge-meta-jvm

alongside with normal versions. • When I try to push to a package which did not exist before, I get 404. Do you know some ways around those problems?

👀 1

Robert Jaros

03/14/2020, 11:28 AM

I had the same problem a few days ago.

altavir

03/14/2020, 11:28 AM

Did you solve it?

Robert Jaros

03/14/2020, 11:28 AM

found an issue https://github.com/gradle/gradle/issues/11412

and a workaround

https://github.com/JetBrains/kotlin-native/pull/3617#issuecomment-558559030

I had no problems pushing new packages.

altavir

03/14/2020, 11:31 AM

Thanks, I will try the workaround. For new packages I will try to debug it

The workaround works, thank you, but I am getting

Could not PUT '<https://api.bintray.com/maven/mipt-npm/dev/dataforge-tables/;publish=0;override=1/hep/dataforge/dataforge-tables/0.1.5-dev-10/dataforge-tables-0.1.5-dev-10.pom>'. Received status code 404 from server: Not Found

for a pachage that does not exist

louiscad

03/14/2020, 11:43 AM

I think you need to create the package beforehand on bintray's web interface.

altavir

03/14/2020, 11:44 AM

Yeah, I can do that, but I thought thay maybe there is a way to create it automatically. Probably bintray plugin is required for that...

Robert Jaros

03/14/2020, 11:45 AM

I confirm I have the same problem when I try to create a new package. I had no new packages earlier.

serebit

03/14/2020, 2:16 PM

Hey, that's my issue! Glad people are managing to find it :D