你怎么用的MSBuild集成常春藤 [英] How do you integrate ivy with MSbuild

查看:220
本文介绍了你怎么用的MSBuild集成常春藤的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

什么办法行之有效你结合IVY +的MSBuild?

What approach has worked well for you combining IVY + msbuild?

我们的目标是IVY集成到C#/ C ++构建依赖解析和发布流程。我们试图在一开始和构建结束其添加到自定义任务,我们曾试图与包装ANT + Apache的蚂蚁DOTNET的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.

其他选项可能是gradle这个,buildr,耙。

Other options might be gradle, buildr, rake.

你用什么?

感谢

彼得

推荐答案

大多数建立技术可以使用在本地目录中找到库。我建议使用命令行常春藤计划填充此,在开始你构建的:

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:

java -jar ivy.jar -ivy ivy.xml -settings ivysettings.xml -retrieve "lib/[conf]/[artifact].[ext]"

您的依赖在被称为标准的ivy文件中列出的的ivy.xml 。远程存储库的协议,位置和布局中描述的 ivysettings.xml

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.

这篇关于你怎么用的MSBuild集成常春藤的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆