冲突的跨版本后缀:com.twitter:util-core [英] Conflicting cross-version suffixes in: com.twitter:util-core

查看:31
本文介绍了冲突的跨版本后缀:com.twitter:util-core的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我升级到 sbt 0.13,这个问题开始出现.我在这里找到了解释:https://groups.google.com/forum/#!topic/simple-build-tool/MoApqIwx4R0

I upgraded to sbt 0.13 and this issue started to pop out. I've found explaination here: https://groups.google.com/forum/#!topic/simple-build-tool/MoApqIwx4R0

我仍在寻找解决方案.

推荐答案

可以通过设置忽略冲突:

You can ignore the conflict by setting:

conflictWarning := ConflictWarning.disable,

可能可以通过配置冲突管理器来解决冲突.SBT 0.13 的冲突管理描述 这里.如果您想要预定义的冲突管理器之一,它们在 ConflictManager 对象中定义:

It might be possible to resolve the conflict by configuring the conflict manager. SBT 0.13's conflict management is described here. If you want one of the predefined conflict managers, they are defined in the ConflictManager object:

object ConflictManager {
    val all = ConflictManager("all")
    val latestTime = ConflictManager("latest-time")
    val latestRevision = ConflictManager("latest-revision")
    val latestCompatible = ConflictManager("latest-compatible")
    val strict = ConflictManager("strict")
    val default = latestRevision
}

例如,要选择最新版本(按修订字符串),您需要将以下内容添加到您的项目设置中:

For example, to select the latest version (by revision string), you would add the following to your project's settings:

conflictManager := ConflictManager.latestRevision

这篇关于冲突的跨版本后缀:com.twitter:util-core的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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