repository issue with conscript and sbt 0.11.3

421 views
Skip to first unread message

Mike Mckibben

unread,
May 25, 2012, 11:43:25 AM5/25/12
to conscri...@googlegroups.com
Hi all. Just thought I'd share the following issue I encountered with conscript when updating to sbt 0.11.3.

$ cs --branch 0.11.3 harrah/xsbt/0.11.3
java.lang.RuntimeException: Expected one of local, maven-local, maven-central, sonatype-oss-releases, sonatype-oss-snapshots, got 'scala-tools-releases'.
at xsbti.Predefined.toValue(Predefined.java:25)
at xsbt.boot.Repository$Predefined$.apply(LaunchConfiguration.scala:70)
at xsbt.boot.ConfigurationParser$$anonfun$getRepositories$1.apply(ConfigurationParser.scala:173)
at xsbt.boot.ConfigurationParser$$anonfun$getRepositories$1.apply(ConfigurationParser.scala:172)
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:194)
at scala.collection.immutable.List.foreach(List.scala:45)
at scala.collection.mutable.FlatHashTable$class.map(Proxy.scala:194)
at scala.collection.immutable.List.map(List.scala:45)
at xsbt.boot.ConfigurationParser$$anonfun$4.apply(ConfigurationParser.scala:67)
at xsbt.boot.ConfigurationParser$$anonfun$processSection$1.apply(ConfigurationParser.scala:101)
at xsbt.boot.ConfigurationParser.process(ConfigurationParser.scala:102)
at xsbt.boot.ConfigurationParser.processSection(ConfigurationParser.scala:101)
at xsbt.boot.ConfigurationParser.xsbt$boot$ConfigurationParser$$apply(ConfigurationParser.scala:60)
at xsbt.boot.ConfigurationParser$$anonfun$apply$3.apply(ConfigurationParser.scala:52)
at xsbt.boot.Using$.withResource(Using.scala:11)
at xsbt.boot.Using$.apply(Using.scala:10)
at xsbt.boot.Configuration$$anonfun$parse$1.apply(Configuration.scala:15)
at xsbt.boot.Using$.withResource(Using.scala:11)
at xsbt.boot.Using$.apply(Using.scala:10)
at xsbt.boot.Configuration$.parse$fcb646c(Configuration.scala:15)
at xsbt.boot.Launch$.apply(Launch.scala:14)
at xsbt.boot.Boot$.runImpl(Boot.scala:25)
at xsbt.boot.Boot$.main(Boot.scala:15)
at xsbt.boot.Boot.main(Boot.scala)
Error during sbt execution: java.lang.RuntimeException: Expected one of local, maven-local, maven-central, sonatype-oss-releases, sonatype-oss-snapshots, got 'scala-tools-releases'.

I fixed the issue by changing the scala-tools-releases repository in the [repositories] section in the launch configuration to be sonatype-oss-releases. Looks like the scala-tools-* predefined repositories are no longer defined in sbt 0.11.3, and we should be using the sonatype-oss-* repositories in our launch configurations instead...

Doug Tangren

unread,
May 25, 2012, 12:22:28 PM5/25/12
to conscri...@googlegroups.com
Maybe it's not directly related but there are some experimental changes [1] Mark just put in for the launcher that may be incompatible with published version conscript uses. You may be referencing something that breaks the published compatibility on that branches launch config.

Mark Harrah

unread,
May 26, 2012, 1:17:07 PM5/26/12
to conscri...@googlegroups.com
On Fri, 25 May 2012 08:43:25 -0700 (PDT)
Mike Mckibben <mikemc...@gmail.com> wrote:

> Hi all. Just thought I'd share the following issue I encountered with
> conscript when updating to sbt 0.11.3.
>
> $ cs --branch 0.11.3 harrah/xsbt/0.11.3
> java.lang.RuntimeException: Expected one of local, maven-local,
> maven-central, sonatype-oss-releases, sonatype-oss-snapshots, got
> 'scala-tools-releases'.

Sorry, we can certainly keep the 'scala-tools-*' names around as aliases for 'sonatype-oss-*'. Can you open a bug with sbt?

-Mark

Nathan Hamblen

unread,
May 28, 2012, 11:15:04 PM5/28/12
to conscri...@googlegroups.com
On 05/26/2012 01:17 PM, Mark Harrah wrote:
> On Fri, 25 May 2012 08:43:25 -0700 (PDT)
> Mike Mckibben<mikemc...@gmail.com> wrote:
>
>> Hi all. Just thought I'd share the following issue I encountered with
>> conscript when updating to sbt 0.11.3.
>>
>> $ cs --branch 0.11.3 harrah/xsbt/0.11.3
>> java.lang.RuntimeException: Expected one of local, maven-local,
>> maven-central, sonatype-oss-releases, sonatype-oss-snapshots, got
>> 'scala-tools-releases'.
> Sorry, we can certainly keep the 'scala-tools-*' names around as aliases for 'sonatype-oss-*'. Can you open a bug with sbt?

I don't think you need to do that, I just need to remove the references
to scala-tools in my launchconfigs. Just did that for conscript.

Nathan
Reply all
Reply to author
Forward
0 new messages