blocks|key|1863140|text|Scala+2.12或2.13|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1863141|快速版本|1863142|Global+/+resolvers+%2B=+"scala-integration"+at
++"https://scala-ci.typesafe.com/artifactory/scala-integration/"
scalaVersion+:=+"2.13.1-bin-abcd123"|code-block|syntax|javascript|1863143|对于2.12夜间版本，用2.12.9代替2.13.1；无论哪种情况，它都是该分支上下一个版本的版本号|offset|length|style|CODE|1863144|对于abcd123，请手动替换最新绿色构建on+the+2.13.x+or+2.12.x+branch+on+Travis-CI的SHA的前7个字符。|1863145|更长的解释|1863146|Scala团队不再发布Scala的-SNAPSHOT版本。(重新开始可能是对社区的贡献；请参阅this+ticket。)|1863147|但该团队确实每晚发布构建，每个构建都有自己的固定版本号。每晚的版本号看起来像2.13.1-bin-abcd123。(-bin-标志着对sbt的二进制兼容性；从2.13.0开始的所有2.13.x版本都是二进制兼容的。)|1863148|以前基于Jenkins的答案不再适用，因为我们(在2018年)将夜间新闻的发布从Jenkins转移到了Travis-CI。|1863149|要告诉sbt使用这些夜间模式之一，您需要做三件事。|1863150|首先，添加保存夜间事件的解析器：|1863151|Global+/+resolvers+%2B=+"scala-integration"+at
++"https://scala-ci.typesafe.com/artifactory/scala-integration/"|1863152|其次，指定Scala版本：|1863153|scalaVersion+:=+"2.13.1-bin-abcd123"|1863154|但这不是真正的版本号。手动替换一个版本号，该版本号包含发布夜间构建的scala/scala+repository中最后一次提交的7个字符的SHA值。查看https://travis-ci.org/scala/scala/branches，您将在2.13.x+(或2.12.x)部分的右上角看到SHA。例如：|1863155|​|1863156|📷|atomic|1863157|1863158|一旦2.13.1发布，夜间的版本号就会跳到2.13.2，以此类推。|1863159|如果有多项目生成，请确保在修改生成定义时跨所有项目设置这些设置。或者，您可以在sbt+shell中使用%2B%2B2.13.1-bin-abcd123+(sbt0.13.x)或%2B%2B2.13.1-bin-abcd123!+(sbt1.x；添加的感叹号是强制使用crossScalaVersions中未包含的版本所必需的)来临时设置它们。|1863160|理想情况下，我们会建议一种自动方式来要求Travis-CI提供正确的SHA。这可能是通过Travis-CI的API实现的，但(据我所知)还没有人研究过它。(有志愿者吗？)|1863161|请注意，我们将这些非正式地称为“夜间”构建，但从技术上讲，这是一个用词不当的说法。所谓的“夜间”是为每个合并的PR构建的。|1863162|Scala+2.11|1863163|没有计划发布更多的2.11.x版本，所以我们(Lightbend的Scala团队)也不再发布2.11夜间新闻。|1863164|entityMap|0|LINK|mutability|MUTABLE|url|https://travis-ci.com/github/scala/scala/branches|1|https://github.com/scala/scala-jenkins-infra/issues/133|2|https://github.com/scala/scala|3|https://travis-ci.org/scala/scala/branches|4|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6af68a50b9bcff806bfdd3ab7368a286.png|imageAlt^0|0|0|0|C|6|K|6|0|2|7|L|17|0|0|0|H|9|1B|B|1|0|12|I|1M|5|0|0|0|0|0|0|0|Y|M|2|24|16|3|0|0|0|1|4|0|0|0|1F|K|2C|L|3H|I|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2D|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|2E|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|2F|8|@$K|2G|L|2H|M|N]|$K|2I|L|2J|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|2K|8|@$K|2L|L|2M|M|N]]|9|@$K|2N|L|2O|1|2P]]|A|$]]|$1|Q|3|R|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2R|8|@$K|2S|L|2T|M|N]]|9|@$K|2U|L|2V|1|2W]]|A|$]]|$1|U|3|V|5|6|7|2X|8|@$K|2Y|L|2Z|M|N]|$K|30|L|31|M|N]]|9|@]|A|$]]|$1|W|3|X|5|6|7|32|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|33|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|34|8|@]|9|@]|A|$]]|$1|12|3|13|5|F|7|35|8|@]|9|@]|A|$G|H]]|$1|14|3|15|5|6|7|36|8|@]|9|@]|A|$]]|$1|16|3|17|5|F|7|37|8|@]|9|@]|A|$G|H]]|$1|18|3|19|5|6|7|38|8|@]|9|@$K|39|L|3A|1|3B]|$K|3C|L|3D|1|3E]]|A|$]]|$1|1A|3|1B|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|1E|7|3G|8|@]|9|@$K|3H|L|3I|1|3J]]|A|$]]|$1|1F|3|1B|5|6|7|3K|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|3M|8|@$K|3N|L|3O|M|N]|$K|3P|L|3Q|M|N]|$K|3R|L|3S|M|N]]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|3U|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3V|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|3W|8|@]|9|@]|A|$]]|$1|1S|3|-4|5|6|7|3X|8|@]|9|@]|A|$]]]|1T|$1U|$5|1V|1W|1X|A|$1Y|1Z]]|20|$5|1V|1W|1X|A|$1Y|21]]|22|$5|1V|1W|1X|A|$1Y|23]]|24|$5|1V|1W|1X|A|$1Y|25]]|26|$5|27|1W|28|A|$29|2A|2B|-4]]]]

<h2>Scala 2.12 or 2.13</h2>
<h3>quick version</h3>
<pre><code>Global / resolvers += &quot;scala-integration&quot; at
  &quot;https://scala-ci.typesafe.com/artifactory/scala-integration/&quot;
scalaVersion := &quot;2.13.1-bin-abcd123&quot;
</code></pre>
<p>for a 2.12 nightly, substitute e.g. <code>2.12.9</code> for <code>2.13.1</code>; in either case, it's the version number of the <em>next</em> release on that branch</p>
<p>for <code>abcd123</code>, manually substitute the first 7 characters of the SHA of the latest green build <a href="https://travis-ci.com/github/scala/scala/branches" rel="nofollow noreferrer">on the 2.13.x or 2.12.x branch on Travis-CI</a>.</p>
<h3>longer explanation</h3>
<p>The Scala team no longer publishes <code>-SNAPSHOT</code> versions of Scala. (Starting that again could be a community contribution; see <a href="https://github.com/scala/scala-jenkins-infra/issues/133" rel="nofollow noreferrer">this ticket</a>.)</p>
<p>But the team does publish nightly builds, each with its own fixed version number. The version number of a nightly looks like e.g. <code>2.13.1-bin-abcd123</code>. (<code>-bin-</code> signals binary compatibility to sbt; all 2.13.x releases since 2.13.0 are binary compatible with each other.)</p>
<p>The old Jenkins-based answer that used to be here no longer works, since we (in 2018) moved publishing of nightlies off Jenkins and onto Travis-CI.</p>
<p>To tell sbt to use one of these nightlies, you need to do three things.</p>
<p>First, add the resolver where the nightlies are kept:</p>
<pre><code>Global / resolvers += &quot;scala-integration&quot; at
  &quot;https://scala-ci.typesafe.com/artifactory/scala-integration/&quot;
</code></pre>
<p>Second, specify the Scala version:</p>
<pre><code>scalaVersion := &quot;2.13.1-bin-abcd123&quot;
</code></pre>
<p>But that isn't a real version number. Manually substitute a version number containing the 7-character SHA of the last commit in the <a href="https://github.com/scala/scala" rel="nofollow noreferrer">scala/scala repository</a> for which a nightly build was published.  Look at <a href="https://travis-ci.org/scala/scala/branches" rel="nofollow noreferrer">https://travis-ci.org/scala/scala/branches</a> and you'll see the SHA in the upper right corner of the 2.13.x (or 2.12.x) section. For example:</p>
<p><a href="https://i.stack.imgur.com/7p2O2.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/7p2O2.png" alt="enter image description here" /></a></p>
<p>As soon as 2.13.1 is released, the version number in the nightly will bump to 2.13.2, and so on.</p>
<p>If you have a multiproject build, be sure you set these settings across all projects when you modify your build definition. Or, you may set them temporarily in the sbt shell with <code>++2.13.1-bin-abcd123</code> (sbt 0.13.x) or <code>++2.13.1-bin-abcd123!</code> (sbt 1.x; the added exclamation point is necessary to force a version not included in <code>crossScalaVersions</code> to be used).</p>
<p>Ideally, we would suggest an automated way to ask Travis-CI for the right SHA. This is presumably possible via Travis-CI's API, but (to my knowledge) nobody has looked into it yet. (Is there a volunteer?)</p>
<p>Note that we call these “nightly” builds informally, but technically it's a misnomer. A so-called “nightly” is built for every merged PR.</p>
<h2>Scala 2.11</h2>
<p>No further 2.11.x releases are planned, so we (the Scala team at Lightbend) aren't publishing 2.11 nightlies anymore, either.</p>


<p>I want to test my code against the latest bleeding edge Scala nightlies.</p>

<p>The <a href="https://stackoverflow.com/q/13433470/86485">answer for Scala 2.10</a> doesn't work anymore.</p>

<p>What do I do?</p>


How do I tell sbt to use a nightly build of Scala 2.12 or 2.13?

我想用最新的尖端Scala工具来测试我的代码。不再工作了。我做什么好？

问如何告诉sbt使用Scala 2.12或2.13的夜间构建？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何告诉sbt使用Scala 2.12或2.13的夜间构建？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何告诉sbt使用Scala 2.12或2.13的夜间构建？
EN