Before you use Pandora Boot to develop High-speed Service Framework (HSF) applications, you must configure the internal repository path and the light-weight configuration center of Enterprise Distributed Application Service (EDAS).

Background information

  • Third-party packages of Spring Cloud for Aliware are released only in the internal repository of EDAS. Therefore, you must configure the internal repository path of EDAS in Maven.
  • The light-weight configuration center must be started for on-premises code development and debugging. The light-weight configuration center provides service discovery and configuration management features.

Configure the internal repository path of EDAS in Maven

Note Only Maven 3.x and later are supported. You must add the internal repository path of EDAS to the configuration file of Maven.
  1. Add the internal repository path of EDAS to the Maven configuration file (stored in in most cases), as shown in the following example:
    <profiles>
        <profile>
            <id>nexus</id>
            <repositories>
                <repository>
                    <id>central</id>
                    <url>https://repo1.maven.org/maven2</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>central</id>
                    <url>https://repo1.maven.org/maven2</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>
        </profile>
        <profile>
            <id>edas.oss.repo</id>
            <repositories>
                <repository>
                    <id>edas-oss-central</id>
                    <name>taobao mirror central</name>
                    <url>http://edas-public.oss-cn-hangzhou.aliyuncs.com/repository</url>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                </repository>
                </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>edas-oss-plugin-central</id>
                    <url>http://edas-public.oss-cn-hangzhou.aliyuncs.com/repository</url>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                </pluginRepository>
            </pluginRepositories>
        </profile>
    </profiles>
    <activeProfiles>
        <activeProfile>nexus</activeProfile>
        <activeProfile>edas.oss.repo</activeProfile>
    </activeProfiles>
  2. In the command-line interface (CLI), run the mvn help:effective-settings command to check whether the settings are added.
    • No errors are reported. This indicates that the format of the settings.xml file is valid.
    • The edas.oss.repo profile is included in profiles. This indicates that the internal repository settings have been added to the profiles.
    • The edas.oss.repo profile is included in activeProfiles. This indicates that the edas.oss.repo internal repository is activated.
    Note If no errors occur after you run the Maven packaging command in the CLI but you cannot use the integrated development environment (IDE) to download the dependencies, close the IDE and restart it. You can also search for the related documentation to obtain the information about how to configure Maven in your IDE.

Configure the light-weight configuration center

For more information about the procedure, see Start the light-weight configuration registry.