Maven Settings中Profile属性无法替换镜像URL，求助原因

问题描述 #

我有如下settings.xml文件，执行mvn clean install命令时，期望镜像的${mirror.url}被Profile中定义的属性替换，但替换未生效，报错日志如下：

<settings>
    <mirrors>
        <mirror>
            <mirrorOf>central</mirrorOf>
            <id>publicGroupProxy</id>
            <name>Proximity mirrored central repository in group public</name>
            <url>${mirror.url}</url>
        </mirror>
    </mirrors>
    <profiles>
        <profile>
            <properties>
                <mirror.url>https://example.com/content/groups/public</mirror.url>
                <repo.url>https://example.com/repository/content/groups/public</repo.url>
            </properties>
            <id>production-repositories</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
            <repositories>
                <repository>
                    <id>production-repository</id>
                    <url>${repo.url}</url>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>production-repository</id>
                    <url>${repo.url}</url>
                </pluginRepository>
            </pluginRepositories>
        </profile>
    </profiles>
    <activeProfiles>
        <activeProfile>production-repositories</activeProfile>
    </activeProfiles>
</settings>

报错日志：

org.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata .../maven-metadata.xml from/to publicGroupProxy (${mirror.url}): Cannot access ${mirror.url} with type default using the available connector factories: BasicRepositoryConnectorFactory

原因解析 #

Maven加载settings.xml的顺序是问题核心：

• Maven会先解析<mirrors>节点，再加载并处理<profiles>中的属性配置。所以当解析镜像的url时，Profile里定义的mirror.url还未被加载，变量自然无法完成替换。
• 而<repositories>和<pluginRepositories>里的${repo.url}能正常替换，是因为这些节点属于Profile内部，会和Profile的属性一起被解析加载。

解决方案 #

方法1：将属性移到全局<properties>节点 #

把mirror.url定义在settings.xml的根级<properties>下（不要放在Profile内部），这样Maven解析镜像时就能读取到该属性：

<settings>
    <!-- 全局属性节点，优先于mirrors被加载 -->
    <properties>
        <mirror.url>https://example.com/content/groups/public</mirror.url>
        <repo.url>https://example.com/repository/content/groups/public</repo.url>
    </properties>
    <mirrors>
        <mirror>
            <mirrorOf>central</mirrorOf>
            <id>publicGroupProxy</id>
            <name>Proximity mirrored central repository in group public</name>
            <url>${mirror.url}</url>
        </mirror>
    </mirrors>
    <profiles>
        <profile>
            <id>production-repositories</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
            <repositories>
                <repository>
                    <id>production-repository</id>
                    <url>${repo.url}</url>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>production-repository</id>
                    <url>${repo.url}</url>
                </pluginRepository>
            </pluginRepositories>
        </profile>
    </profiles>
    <activeProfiles>
        <activeProfile>production-repositories</activeProfile>
    </activeProfiles>
</settings>

方法2：命令行直接传递属性 #

执行Maven命令时手动指定mirror.url的值，这种方式优先级最高：

mvn clean install -Dmirror.url=https://example.com/content/groups/public

方法3：结合Profile激活的环境属性（多场景适配） #

如果需要根据不同环境切换镜像，可以用系统属性激活Profile，同时在全局属性中引用：

<settings>
    <properties>
        <mirror.url>${env.mirror-url}</mirror.url>
    </properties>
    <mirrors>
        <mirror>
            <mirrorOf>central</mirrorOf>
            <id>publicGroupProxy</id>
            <name>Proximity mirrored central repository in group public</name>
            <url>${mirror.url}</url>
        </mirror>
    </mirrors>
    <profiles>
        <profile>
            <id>production-repositories</id>
            <activation>
                <property>
                    <name>env</name>
                    <value>prod</value>
                </property>
                <activeByDefault>true</activeByDefault>
            </activation>
            <properties>
                <env.mirror-url>https://example.com/content/groups/public</env.mirror-url>
                <repo.url>https://example.com/repository/content/groups/public</repo.url>
            </properties>
            <repositories>
                <repository>
                    <id>production-repository</id>
                    <url>${repo.url}</url>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>production-repository</id>
                    <url>${repo.url}</url>
                </pluginRepository>
            </pluginRepositories>
        </profile>
    </profiles>
</settings>

执行命令时指定环境：

mvn clean install -Denv=prod

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