Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 10 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(2)
我不确定改用甘特能解决你的问题。 Gant 只是用 groovy 而不是 xml 编写构建文件。我认为你的问题更多地在于你使用蚂蚁的方式。没有更多细节很难说,但是像“愚蠢的重复量”和“复制构建文件”这样的短语让我认为你可以更有效地使用 ant。
如果您还没有这样做,请查看您的 ant 任务,看看是否可以重构它们,从而消除重复。另外,如果您还没有看到 ant 的 -find 选项,请查看它。您不需要复制构建文件。
顺便说一句,Ivy 用于依赖管理,而不是构建。
I'm not sure switching to gant will solve your problems. Gant is just writing build files in groovy instead of xml. I think your issue lays more in the way you're using ant. Hard to say without more details, but phrases like "dumb amount of duplication" and "copying build files around" make me think you could be using ant more efficiently.
If you haven't already, look at your ant tasks, and see if you can refactor them so eliminate that duplication. Also, checkout the -find option to ant if you haven't seen it already. You shouldn't need to be copying build files around.
BTW, Ivy is for dependency management, not building.
我知道我们公司里以 Java 为生的人对 Ivy 非常信赖,但没有任何使用经验,我没有足够的事实来支持这个建议和技术论证。他们确实提到,与他们之前使用的 Ant 相比,缺乏重复是一个优点。买者自负。
I know that people in our company who do Java for a living swear by Ivy, but not having any experience with it, I don't have enough facts to back this suggestion up with technical arguments. They did mention lack of duplication as a plus though compared to Ant they used before. Caveat emptor.