Anyone had any experience using Jitpack with a mul...
# multiplatform
s
Anyone had any experience using Jitpack with a multiplatform library? Gradle is refusing to resolve my snapshots despite seemingly producing the correct artifacts and maven components.
e
You could be hitting this issue: https://github.com/gradle/gradle/issues/9462
k
Can't use jitpack with multiplatform
s
@kpgalligan Ah, bummer. Is there a post about this somewhere? I'd like to read if they're planning on supporting it at some point in the future. It's strange that you aren't able to use Multiplatform with Jitpack when it appears to be generating the artifacts and metadata correctly for each target, just unable to find them.
@Erik Christensen hmm, looks like that issue was fixed, but I'll see if there's anything there that might help. thank you!
k
I don’t know, to be honest. Things change all the time, so my info may be outdated. I’m giving a talk on library tomorrow, so if jitpack works now, let me know
e
@Shan: Sort of. Gradle 5.6.3+ can consume SNAPSHOT artifacts with Gradle metadata properly, but only Gradle 6 can generate them. Haven't used jitpack though, so I don't know if there's a more general issue with using it.
s
Gonna try pushing with Gradle 6.0 on both of my mpp and see if that changes anythhing
Did not realise that 6.0 stable was released like an hour ago
k
s
Ooh thank you.
I have upgrade both of my projects to Gradle 6.0, but now am having a different problem trying to build, this time I think it's a Jitpack issue but not sure.
Copy code
> Could not create task ':DependenciesReport'.
   > Unnecessarily replacing a task that does not exist is not supported.  Use create() or register() directly instead.  You attempted to replace a task named 'DependenciesReport', but there is no existing task with that name.
Wondering if DependenciesReport was deprecated..
Alright well maybe it's not a Jitpack specific issue, looks like if I take out the dependency it is still having the issue, so will have to debug further.
k
I’m guessing v6 may not work super smooth
s
Looks like the metadatas generated from Gradle 6.0 did not do the trick unfortunately. Thinking that it's a Jitpack issue. Ah well.