有没有办法配置 Ivy 以从分支获取依赖项，而无需编辑每个相关依赖项？
我这里有许多项目，它们之间以及与外部库之间都有依赖关系。依赖管理是通过 ivy 和我们自己的存储库完成的。我们最近不得不进行分支，因为项目的一个版本正在进行质量检查，而另一个版本则正在进行当前的开发。
问题是，如果不将分支属性添加到每个内部依赖项，我无法找到在新分支中使用 ivy 的方法。
我考虑过将分支属性添加到解析任务并激活内联模式，但它也适用于外部库，这是不正确的。但是向每个内部部门添加分支属性会很麻烦。
I have a number of projects here that have dependencies between each other as well as to external libraries. Dependency management is done with ivy and our own repository. We recently had to branch because there is one version of the projects that is in QA and another one where current development is done.
The problem is that I can't find a way to use ivy in the new branch without adding the branch attribute to every internal dependency.
I thought about adding the branch attribute to the resolve task and activating inline mode but then it would also apply to the external libraries which is not correct. But adding the branch attribute to every interal dep would be cumbersome.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
那么您想区分从分支发布的工件和从主干发布的工件吗？
我使用 ivy buildnumber 任务来增加版本号每份出版物的。
分支使用 project.version 属性来指示它们源自哪个版本的主干分支，例如：
这种方法意味着已发布的工件具有以下修订号：
而主干版本将是：
So you want to differentiate between artefacts published from the branch and artefacts published from the trunk?
I use the ivy buildnumber task to increment the release number of each publication.
Branches use a project.version property that indicates which version of the trunk branch they originate from, for example:
This approach means published artifacts have the following revision numbers:
Whereas trunk releases would be: