如何将ivy与MSbuild集成
哪种方法对您组合 IVY + msbuild 效果最好？
我们的目标是将 IVY 集成到 C#/C++ 构建过程中，以进行依赖项解析和发布。我们尝试在构建的开始和结束时将其添加到自定义任务中，并尝试使用 ant+ apache-ant-dotnet 包装 msbuild 调用。
其他选项可能是 gradle、buildr、rake。
你用什么？
谢谢
彼得
What approach has worked well for you combining IVY + msbuild?
Our goal is to integrate IVY into the C#/C++ build process for dependency resolution and publishing. We have tried adding it to custom tasks at the beginning and end of the build and we have tried wrapping the msbuild calls with ant+ apache-ant-dotnet.
Other options might be gradle, buildr, rake.
What do you use?
Thanks
Peter
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
大多数构建技术都可以使用本地目录中的库。我建议使用 命令行 ivy 程序 来填充在构建开始时：
您的依赖项列在名为 ivy.xml 的标准 ivy 文件中。远程存储库的协议、位置和布局在 ivysettings.xml 中描述。
这种方法的优点（相对于切换到 Gradle 等）是，您不会尝试替换现有的构建工具。 Ivy 只关心管理依赖关系。
Most build technologies can use libraries found in a local directory. I'd suggest using the command-line ivy program to populate this, at the start of your build:
Your dependencies are listed in a standard ivy file called ivy.xml. The protocol, location and layout of your remote repository is described in ivysettings.xml
The advantage of this approach (as opposed to switching to Gradle, etc) is that you're not trying to replace your existing build tool. Ivy is solely concerned with managing dependencies.
我的团队已经使用 Ivy for .NET 几年了，非常成功。我知道还有其他几个可以对其投信任票的人。
独立使用它。将调用包装到 msbuild 任务中。无需使用 Ant 集成。
My team has been using Ivy for .NET for a couple of years very successfully. I know several more that give it a vote of confidence.
Use it standalone. Wrap calls into msbuild tasks. No need to use Ant integration.