【发布时间】:2015-09-01 18:19:10
【问题描述】:
在我们的 pom 文件中,我们有一个特殊的配置文件,允许我们将工件部署到我们的内部 maven 存储库以及位于谷歌云上的外部存储库。
<distributionManagement>
<repository>
<uniqueVersion>false</uniqueVersion>
<id>nexus</id>
<name>Internal Releases</name>
<url>http://internal_instance_ip/nexus/content/repositories/releases</url>
<layout>default</layout>
</repository>
<snapshotRepository>
<uniqueVersion>true</uniqueVersion>
<id>nexus-snapshots</id>
<name>Internal Snapshots</name>
<url>http://internal_instance_ip/nexus/content/repositories/snapshots</url>
<layout>default</layout>
</snapshotRepository>
</distributionManagement>
<profiles>
<profile>
<id>gce</id>
<distributionManagement>
<repository>
<uniqueVersion>false</uniqueVersion>
<id>nexus-gce</id>
<name>External Releases</name>
<url>https://gce_instance_ip/content/repositories/releases</url>
<layout>default</layout>
</repository>
<snapshotRepository>
<uniqueVersion>true</uniqueVersion>
<id>nexus-snapshots-gce</id>
<name>External Snapshots</name>
<url>https://gce_instance_ip/content/repositories/snapshots</url>
<layout>default</layout>
</snapshotRepository>
</distributionManagement>
</profile>
</profiles>
当我尝试部署项目时,它抱怨:
Return code is: 413, ReasonPhrase: Request Entity Too Large.
该项目有很多模块,有问题的不需要部署到谷歌云上。如何排除该模块部署到谷歌云存储库但仍部署到内部存储库?
【问题讨论】:
标签: maven google-cloud-platform