Gradle多Java项目Docker构建最佳实践：本地依赖构建问题

问题 #

我有一个Gradle Java项目Project-A，依赖另外两个Gradle Java项目Project-B和Project-C。三个项目均通过build.gradle本地构建，Project-A的build.gradle包含：

implementation project(':Project-B')
implementation project(':Project-C')

其settings.gradle包含：

include ':Project-B'
project(':Project-B').projectDir = new File(settingsDir, '../Project-B')
include ':Project-C'
project(':Project-C').projectDir = new File(settingsDir, '../Project-C')

三个项目分别拥有独立私有Git仓库（未来会有其他项目依赖B和C）。本地运行gradle build可正常构建，但尝试Docker化Project-A时，其Dockerfile如下：

FROM gradle:jdk11-alpine AS builder
COPY ./ ./
RUN gradle build

FROM adoptopenjdk/openjdk11:jre-11.0.6_10-alpine
COPY --from=builder *.jar Project-A.jar
CMD ["java -jar Project-A.jar"] 

执行docker build .时出现错误：

#11 51.17 FAILURE: Build failed with an exception.
#11 51.17
#11 51.17 * What went wrong:
#11 51.17 Could not determine the dependencies of task ':bootJar'.
#11 51.17 > Could not resolve all task dependencies for configuration ':runtimeClasspath'.
#11 51.17    > Could not resolve project :project-B.
#11 51.17      Required by:
#11 51.17          project :
#11 51.17       > No matching configuration of project :project-B was found. The consumer was configured to find a runtime of a library compatible with Java 11, packaged as a jar, preferably optimized for standard JVMs, and its dependencies declared externally but:
#11 51.17           - None of the consumable configurations have attributes.
#11 51.17    > Could not resolve project :project-C.
#11 51.17      Required by:
#11 51.18          project :
#11 51.18       > No matching configuration of project :project-C was found. The consumer was configured to find a runtime of a library compatible with Java 11, packaged as a jar, preferably optimized for standard JVMs, and its dependencies declared externally but:
#11 51.18           - None of the consumable configurations have attributes.

其中bootJar任务配置为：

bootJar {
    archiveBaseName = 'Project-A'
    archiveVersion =  '0.1.0'
}

由于Project-B和C的Jar包未发布到任何仓库，需随Project-A一起构建，请问Docker构建这类本地依赖Gradle项目的最佳实践是什么？缺失了哪些COPY步骤？

解决方案 #

核心原因 #

Docker构建时仅复制了Project-A的代码，但Project-B、Project-C的代码不在Docker构建上下文内，导致Gradle找不到依赖项目的配置文件，进而抛出配置匹配失败的错误。

具体修正与最佳实践 #

1. 补全依赖项目的COPY步骤

需要将Project-B和Project-C的代码复制到容器内与本地一致的路径（匹配settings.gradle中的相对路径配置），修改Dockerfile的builder阶段：

FROM gradle:jdk11-alpine AS builder
# 创建与本地一致的项目目录结构
RUN mkdir -p /home/gradle/workspace/Project-A /home/gradle/workspace/Project-B /home/gradle/workspace/Project-C
# 复制Project-A代码到容器对应目录
COPY ./ /home/gradle/workspace/Project-A/
# 复制Project-B代码到容器内的../Project-B路径
COPY ../Project-B /home/gradle/workspace/Project-B/
# 复制Project-C代码到容器内的../Project-C路径
COPY ../Project-C /home/gradle/workspace/Project-C/
# 切换到Project-A目录执行构建
WORKDIR /home/gradle/workspace/Project-A
# 加上--no-daemon避免Gradle后台进程残留
RUN gradle build --no-daemon

注意：执行docker build时，需要将构建上下文切换到三个项目的共同父目录，否则无法访问../Project-B和../Project-C路径。如果无法切换上下文，可使用Docker 23.0+支持的--build-context参数指定各项目路径：

docker build --build-context a=./Project-A --build-context b=./Project-B --build-context c=./Project-C -f Project-A/Dockerfile .

此时Dockerfile中的COPY指令需对应修改为COPY --from=a ./ /home/gradle/workspace/Project-A/这类格式。

2. 修正Jar包复制路径与CMD指令

原Dockerfile中COPY --from=builder *.jar会匹配容器内所有Jar包，容易复制无关文件；同时CMD指令格式错误（不能将整个命令作为单个字符串）。修正如下：

FROM adoptopenjdk/openjdk11:jre-11.0.6_10-alpine
# 精确复制Project-A构建后的Jar包（对应bootJar配置的文件名）
COPY --from=builder /home/gradle/workspace/Project-A/build/libs/Project-A-0.1.0.jar Project-A.jar
# 使用数组格式的CMD指令，避免Shell解析问题
CMD ["java", "-jar", "Project-A.jar"]

3. 长期优化方案：发布依赖到私有仓库

考虑到未来会有其他项目依赖Project-B和Project-C，建议搭建私有Maven/Gradle仓库（如Nexus、Artifactory），将Project-B、Project-C构建后发布到私有仓库，Project-A直接通过仓库坐标引用依赖。这样Docker构建时无需复制依赖项目代码，只需在build.gradle中配置私有仓库地址即可，更贴合标准化CI/CD流程。

4. 可选方案：使用Gradle复合构建

如果不想调整Docker上下文，可在Project-A的settings.gradle中使用复合构建方式引用依赖项目，但本质仍需将Project-B、Project-C的代码复制到容器内，操作逻辑与第一种方案一致。

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