Why can't I download JAR files for my EDAS project?
This almost always comes down to one of two things: a missing dependency declaration in pom.xml, or a Maven repository configuration issue in settings.xml. Work through the checks below in order.
Step 1: Verify the dependency declarations in pom.xml
Open your project's pom.xml and confirm that the required Enterprise Distributed Application Service (EDAS) dependencies are declared. Two common ones:
<dependency>
<groupId>com.alibaba</groupId>
<artifactId>hsf.schema</artifactId>
<version>edas1.0.0</version>
</dependency><dependency>
<groupId>com.alibaba.edas</groupId>
<artifactId>edas-sdk</artifactId>
<version>1.5.0</version>
</dependency>If either dependency is missing, add it and re-run your build. To confirm Maven can resolve them, run:
mvn dependency:treeThis prints the full dependency tree and shows exactly which artifacts resolved successfully and which failed.
Step 2: Check the repository configuration in settings.xml
If the dependencies are declared but Maven still cannot find the JAR files, the problem is usually in your repository configuration.
Open your settings.xml file (typically at ~/.m2/settings.xml) and check the repositories configuration. Maven resolves dependencies in the following order:
Local repository (
~/.m2/repository)Repositories defined in
settings.xml(global, then user-level)Repositories defined in
pom.xml(project, parent POMs, super POM)Maven Central (default fallback)
Mirrors, if configured, are applied before any remote repository is contacted. A mirror that overrides central or uses <mirrorOf>*</mirrorOf> can silently block access to other repositories, including any repository that hosts EDAS artifacts.
If you use a self-built Maven repository, it likely does not contain the EDAS-specific JARs. Add the repository that hosts EDAS artifacts alongside your internal repository, or download the required JARs from the Maven repository official website and install them into your local or self-built repository manually.
Step 3: Diagnose with verbose output
If the first two steps do not resolve the issue, run Maven with debug output to see exactly where it tries to download each artifact from:
mvn dependency:resolve -XLook for lines that show the repository URLs Maven is querying. To review your effective repository and mirror configuration in one place, run:
mvn help:effective-settingsThis shows the merged result of your global and user-level settings.xml files, including all active mirrors and repositories.