将 Maven 与 Sourceforge.net 结合使用
对于使用 Maven 的新项目，我想在 pom.xml 中添加 distributionManagement 配置，它将将该项目与 Sourceforge.net 文件上传系统连接起来。
我找到了此信息（2007 年），它仍然有效吗？或者您知道更新的资源吗？
http://docs.codehaus.org/display/MAVENUSER/MavenAndSourceforge
For a new project which uses Maven I would like to add distributionManagement configuration in the pom.xml which will connect the project with the Sourceforge.net file upload system.
I have found this information (of 2007), is it still valid or do you know updated resources?
http://docs.codehaus.org/display/MAVENUSER/MavenAndSourceforge
Related question: How can I deploy artifacts from a Maven build to the SourceForge File Release System?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这看起来是正确的。但请注意，它仅描述部署站点工件，而不是项目工件（JAR 和 POM）。虽然您可以使用 Maven 来部署您的工件，但我不确定您是否愿意这样做——Maven 目录结构与 SourceForge 结构（每个版本一个目录）不同。
如果您希望将项目版本部署到 Maven Central，请阅读以下内容：http://maven.apache.org/guides/mini/guide-central-repository-upload.html
该流程在过去一年左右发生了变化。曾经，您可以请求将您的项目添加到夜间 rsync 作业中，但显然现在您必须直接部署到可识别的存储库。考虑到 rsync 作业失败的次数，难怪他们决定更改流程......
This looks correct. However, note that it only describes deploying the site artifacts, not the project artifacts (JAR and POM). And while it's possible that you could use maven to deploy your artifacts, I'm not sure that you'd want to -- the Maven directory structure is different from the SourceForge structure (of one directory per release).
If you're looking to deploy your project releases to Maven Central, read this: http://maven.apache.org/guides/mini/guide-central-repository-upload.html
The process has changed in the last year or so. At one time you could request that your project be added to a nightly rsync job, but apparently now you have to deploy directly to a recognized repository. Given the number of times that rsync job would fail, it's no wonder they decided to change the process ...