updates for 0.11.2

Community/Changes.md

@@ -1,3 +1,26 @@
+### 0.11.1 to 0.11.2
+ 
+Notable behavior change:
+
+ * The local Maven repository has been removed from the launcher's list of default repositories, which is used for obtaining sbt and Scala dependencies.  This is motivated by the high probability that including this repository was causing the various problems some users have with the launcher not finding some dependencies ([#217]).
+
+Fixes:
+
+ * [#257] Fix invalid classifiers in pom generationx (Indrajit)
+ * [#255] Fix scripted plugin descriptor (Artyom)
+ * Fix forking git on windows (Stefan, Josh)
+ * [#261] Fix whitespace handling for semicolon-separated commands
+ * [#263] Fix handling of dependencies with an explicit URL
+ * [#272] Show deprecation message for `project/plugins/`
+
+[#217]: https://github.com/harrah/xsbt/issues/217
+[#255]: https://github.com/harrah/xsbt/issues/255
+[#257]: https://github.com/harrah/xsbt/issues/257
+[#263]: https://github.com/harrah/xsbt/issues/263
+[#261]: https://github.com/harrah/xsbt/issues/261
+[#272]: https://github.com/harrah/xsbt/issues/272
+
+
 ### 0.11.0 to 0.11.1
 
 Breaking change:

Community/Nightly-Builds.md

@@ -14,4 +14,4 @@ Related to the third point, remember that an `sbt.version` setting in `<build-ba
 
 A nightly launcher jar should be able to launch previous stable 0.11.x versions of sbt (it is a bug otherwise).
 
-However, to reduce problems, it is recommended to not use a launcher jar for one nightly version to launch a different nightly version of sbt.  That is, if you have launcher `0.11.2-20110828-110226`, only specify `0.11.0`, `0.11.1`, and `0.11.2-20110828-110226` in a `project/build.properties` file.
+However, to reduce problems, it is recommended to not use a launcher jar for one nightly version to launch a different nightly version of sbt.  That is, if you have launcher `0.11.3-20110828-110226`, only specify `0.11.0`, `0.11.1`, `0.11.2`, and `0.11.3-20110828-110226` in a `project/build.properties` file.

Detailed-Topics/Launcher.md

@@ -92,14 +92,13 @@ The default configuration file for sbt looks like:
 [app]
   org: org.scala-tools.sbt
   name: sbt
-  version: read(sbt.version)[0.11.1]
+  version: read(sbt.version)[0.11.2]
   class: ${sbt.main.class-sbt.xMain}
   components: xsbti,extra
   cross-versioned: true
 
 [repositories]
   local
-  maven-local
   typesafe-ivy-releases: http://repo.typesafe.com/typesafe/ivy-releases/, [organization]/[module]/[revision]/[type]s/[artifact](-[classifier]).[ext]
   maven-central
   scala-tools-releases
@@ -200,12 +199,11 @@ Next, define a configuration file for the launcher.  For the above class, it mig
 [app]
   org: org.scala-tools.sbt
   name: xsbt-test
-  version: 0.11.1
+  version: 0.11.2
   class: xsbt.test.Main
   cross-versioned: true
 [repositories]
   local
-  maven-local
   maven-central
   scala-tools-releases
 #  scala-tools-snapshots

Detailed-Topics/Migrating-from-SBT-0.7.x-to-0.10.x.md

@@ -15,7 +15,7 @@ sbt 0.11's many new capabilities can be a bit overwhelming, but this page should
 Reading the [[Getting Started Guide|Getting Started Welcome]] will
 probably save you a lot of confusion.
 
-# Step 2: Install sbt 0.11.1
+# Step 2: Install sbt 0.11.2
 
 Download sbt 0.11 as described on [[the setup page|Getting Started Setup]].
 
@@ -75,7 +75,7 @@ scalaVersion := "2.9.1"
 Currently, a `project/build.properties` is still needed to explicitly select the sbt version.  For example:
 
 ```text
-sbt.version=0.11.1
+sbt.version=0.11.2
 ```
 
 ## Run sbt 0.11

Detailed-Topics/Scripts.md

@@ -21,7 +21,7 @@ In addition, there is a [setup script] for the script mode that only requires a
 Install [conscript].
 
 ```
-cs harrah/xsbt --branch v0.11.1
+cs harrah/xsbt --branch v0.11.2
 ```
 
 This will create two scripts: `screpl` and `scalas`.

Extending/Input-Tasks.md

@@ -52,11 +52,11 @@ val parser: Initialize[State => Parser[(String,String)]] =
 
 This Parser definition will produce a value of type `(String,String)`.
 The input syntax isn't very flexible; it is just a demonstration.
-It will produce one of the following values for a successful parse (assuming the current Scala version is 2.9.1, the current sbt version is 0.11.1, and there are 3 commands left to run):
+It will produce one of the following values for a successful parse (assuming the current Scala version is 2.9.1, the current sbt version is 0.11.2, and there are 3 commands left to run):
 
 ```scala
 ("scala", "2.9.1")
-("sbt", "0.11.1")
+("sbt", "0.11.2")
 ("commands", "3")
 ```
 

FAQ.md

@@ -19,7 +19,7 @@
 [mailing list]: http://groups.google.com/group/simple-build-tool/topics
 [migration page]: https://github.com/harrah/xsbt/wiki/Migrating-from-SBT-0.7.x-to-0.10.x
 [original proposal]: https://gist.github.com/404272
-[sbt-launch.jar]: http://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbt/sbt-launch/0.11.1/sbt-launch.jar
+[sbt-launch.jar]: http://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbt/sbt-launch/0.11.2/sbt-launch.jar
 [xsbt-web-plugin]: https://github.com/siasia/xsbt-web-plugin
 [xsbt-webstart]: https://github.com/ritschwumm/xsbt-webstart
 [xsbti.ComponentProvider]: http://harrah.github.com/xsbt/latest/api/xsbti/ComponentProvider.html

Getting-Started/Getting-Started-Hello.md

@@ -61,7 +61,7 @@ You can force a particular version of sbt by creating a file `hello/project/buil
 In this file, write:
 
 ```text
-sbt.version=0.11.1
+sbt.version=0.11.2
 ```
 
 From 0.10 onwards, sbt is 99% source compatible from release to release. Still,

Getting-Started/Getting-Started-Setup.md

@@ -1,4 +1,4 @@
-[sbt-launch.jar]: http://typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-tools.sbt/sbt-launch/0.11.1/sbt-launch.jar
+[sbt-launch.jar]: http://typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-tools.sbt/sbt-launch/0.11.2/sbt-launch.jar
 
 # Setup