从JavaScript转Scala/Java生态：依赖管理问题求助与解析

Hey there! Let's break down what's going on with Java/Scala dependency management since you're coming from the simpler npm/yarn world—your confusion makes total sense because the ecosystem works quite differently.

The Big Difference from npm/Yarn #

Unlike npm/yarn, which relies on a single default public registry, the Java/Scala ecosystem doesn't have an official universal public repository. Instead, multiple independent public repositories exist, and build tools only check a small set of "default" ones unless you explicitly tell them to look elsewhere.

Default Repositories for Common Build Tools #

Let's clarify what each tool checks by default:

• Maven: Only checks Maven Central (the largest and most widely used repository, run by the Apache Software Foundation).
• Gradle: Historically included both Maven Central and JCenter (a popular alternative repository), though newer Gradle versions may have removed JCenter by default since it's no longer accepting new packages.
• SBT: By default checks Maven Central plus a few Scala-specific repositories (like Typesafe's repo for frameworks such as Play/Akka).

Why Your Specific Issues Happened #

Let's unpack your two examples:

1. Apollo Android 0.4.3: This version was only published to JCenter, not Maven Central. Since Maven and SBT don't check JCenter by default, they couldn't locate it. Gradle worked once you added jcenter() because that told it to scan this extra repository.
2. SocketCluster Client Java: This package is only hosted in a custom Bintray repository maintained by the package author, which none of the build tools check by default. That's why Maven and SBT couldn't find it unless you manually added the repo URL to your config.

How to Add Custom Repositories in Each Tool #

When you need a package from a non-default repo, you have to explicitly add the repository URL to your build configuration:

Maven (pom.xml) #

Add a <repositories> block inside your project's <project> tag:

<repositories>
  <!-- Example for SocketCluster's custom repo -->
  <repository>
    <id>bintray-sacoo7</id>
    <url>https://dl.bintray.com/sacoo7/Maven</url>
  </repository>
</repositories>

Gradle (build.gradle) #

Add the repo to the repositories section:

repositories {
  mavenCentral()
  jcenter() // For packages hosted in JCenter
  maven { url "https://dl.bintray.com/sacoo7/Maven" } // Add custom repository
}

SBT (build.sbt) #

Use the resolvers setting to add new repositories:

// Add JCenter repository
resolvers += Resolver.jcenterRepo
// Add SocketCluster's custom repository
resolvers += "Bintray Sacoo7" at "https://dl.bintray.com/sacoo7/Maven"

Best Practices to Avoid Headaches #

• Prioritize Maven Central: It's the most stable and widely supported repository—most popular packages are published here.
• Check package documentation: Always verify where the package author publishes their artifacts; they'll usually mention which repo to add if it's not in Maven Central.
• Use search tools: Tools like Maven Central Search (for Java packages) or Scaladex (for Scala packages) let you confirm if a package exists in a default repo and get its correct coordinates.
• Monitor repository statuses: Some repos (like JCenter) are no longer accepting new packages, so newer versions of a package might have moved to Maven Central or another active repo.

Glad you got the SBT issue sorted by adding JCenter! Now that you understand the repository mechanics, you'll be able to troubleshoot these dependency problems much more easily.

内容的提问来源于stack exchange，提问作者Roniel