Apache Archiva 的 Maven 部署失败
我有一个 Maven 项目，它生成一个 413.06 KB jar 文件。我必须将它部署在基于 Apache Archiva 的托管存储库上。我尝试部署不同的版本，它创建了所需的布局和结构，上传了一些文件，甚至上传了 200~ KB 的 jar。每次 jar 文件大小发生变化但总是无法上传 413.06 KB jar 文件。
信息：-
- 我正在运行独立的 Archiva
- ，我已向 Global Repository Manager 提供访客帐户“存储库管理器 - MYREPO”
- 我还尝试在 Archiva 中使用一个具有“存储库管理器 - MYREPO”权限的单独帐户，并在 maven 的 settings.xml 文件中对其进行配置以设置自定义超时。
我收到以下错误
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
(default-deploy) on project SharedshelfRepository: Error deploying artifact: Transfer error:
The server did not respond within the configured timeout. -> [Help 1]
I have a Maven project which generates a 413.06 KB jar file. I have to deploy it on Apache Archiva based managed repository. I have tried to deploy different versions, and it created required layout and structure, uploaded some files, even it uploaded that jar with 200~ KB. every time the jar file size changes but always it fails to upload 413.06 KB jar file.
Information:-
- I am running standalone Archiva
- I have given guest account to Global Repository Manager & "Repository Manager - MYREPO"
- I have also tried a separate account in Archiva with "Repository Manager - MYREPO" rights and configured it in maven's settings.xml file to set custom timeout.
I am getting following error
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
(default-deploy) on project SharedshelfRepository: Error deploying artifact: Transfer error:
The server did not respond within the configured timeout. -> [Help 1]
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这可能是maven-deploy-plugin问题，资源插件本身需要几个依赖项，尝试手动jar nad p
that might be maven-deploy-plugin issue, resources plugin itself needs several dependencies,try manually jar nad p
您使用什么版本的 Maven？您可以尝试 3.0.4，因为它有不同的 HTTP 库。我也不确定超时时发生的情况是否有更多上下文（似乎更多是面向请求而不是面向部署，并且部署确实请求一些元数据）。
我看不出您需要更改超时，因为任何默认值都不适用于如此小的文件。失败需要多长时间？
What version of Maven are you using? You might try 3.0.4 as it has a different HTTP library. I'm also not sure if there's more context for what was happening when it timed out (it seems more request oriented rather than deploy oriented, and deploy does request some metadata).
I can't see that you'd need to alter the timeout, as none of the defaults should apply to such a small file. How long does it take to fail?