6 ms·

I'm not convinced this means the death of Maven Central, but I'll start publishing to both either way.

• djsumdog 7y ago
  Yea same here. There are way too many workflows already setup around Maven Central. People publish to it from Scala/SBT, Gradle, Clojure/Leiningen, Kotlin, etc. It's not going to be going anywhere any time soon.
  • mygo 7y ago
    those same workflows can be published for github if enough demand
  • SOLAR_FIELDS 7y ago
    Exactly. It’s nice to have competition in the Java package space aside from Maven, Jfrog Artifactory and Nexus. It will take time to build up network effects for Github but if they make a good product I could see it happening eventually. We use Artifactory where I work and the generic aspect of it plus the ecosystem integrations are super nice. I can publish docker images, regular zip files, jar files, Python packages etc and use the same tooling for all of that. GitHub should really push for the one-stop-shop approach here because I feel like that’s going to be their major competitive advantage. That’s where Gitlab has been playing too so I wouldn’t be surprised to see a similar product from them in the near future.
    • SOLAR_FIELDS 7y ago
      Too late for me to edit, but it looks like gitlab has been working on this too and published a response: https://about.gitlab.com/2019/05/10/github-adds-package-registry/ https://about.gitlab.com/2019/05/10/github-adds-package-regi... It looks like from that post they only support Docker, Maven and NPM right now so they also have some catching up to do in the genericization world.
  • tomnipotent 7y ago
    Where do you think most of those project's are managing their code? And of those, what percentage are already publishing releases on GH? I'm willing to wager the migration will be much faster than you think.