scalacenter
github.com/nafg repos are stale
https://index.scala-lang.org/nafg/slick-migration-api/slick-migration-api is way outdated, and many other repos are missing
(I don't maintain Scaladex, but) I was looking for clues as to what the cause might be, and I noticed that Scaladex's suggested sbt incantation is:
libraryDependencies += "io.github.nafg" %% "slick-migration-api" % "0.4.2"
resolvers += Resolver.bintrayRepo("naftoligug", "maven")
The resolvers += ... bit caught my eye. I wonder if this is somehow a Bintray vs. Sonatype issue. The library is available on Maven Central, as we see at e.g. https://search.maven.org/artifact/io.github.nafg.slick-migration-api/slick-migration-api_2.13/0.8.2/jar
did the way you publish the library change after 0.4.2, and maybe that's a clue as to why Scaladex is confused here?
No it changed long after that. Up to 0.8.0 was published to bintray. Also it's synced to jcenter.
On Sun, Mar 21, 2021, 6:12 PM Seth Tisue @.***> wrote:
(I don't maintain Scaladex, but) I was looking for clues as to what the cause might be, and I noticed that Scaladex's suggested sbt incantation is:
libraryDependencies += "io.github.nafg" %% "slick-migration-api" % "0.4.2" resolvers += Resolver.bintrayRepo("naftoligug", "maven")
I wonder if this is somehow a Bintray vs. Sonatype issue. The library is available on Maven Central, as we see at e.g. https://search.maven.org/artifact/io.github.nafg.slick-migration-api/slick-migration-api_2.13/0.8.2/jar
did the way you publish the library change after 0.4.2, and maybe that's a clue as to why Scaladex is confused here?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/scalacenter/scaladex/issues/657#issuecomment-803668754, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAYAUHH4ZFWS4EHRU3TB2DTEZVM7ANCNFSM4ZR6VGKA .
Thanks for reporting.
The bintray repos have not been synced since Sep 2018 and I cannot promise anything on when we will try to run this again.
If your libraries are published to Maven Central they should be automatically indexed in Scaladex. But it seems that the scm field in the pom file points to gitlab rather than github. That could explain why they do not appear in the project page. You can fix this by "claiming" those artifacts in https://github.com/scalacenter/scaladex-contrib
