From 00504bb3f1f24c8ce057ada03ac4a871d4a9025b Mon Sep 17 00:00:00 2001
From: Mark Harrah <dmharrah@gmail.com>
Date: Sun, 27 Nov 2011 18:06:11 -0500
Subject: [PATCH] updates for 0.11.2

---
 Community/Changes.md                          | 23 +++++++++++++++++++
 Community/Nightly-Builds.md                   |  2 +-
 Detailed-Topics/Launcher.md                   |  6 ++---
 .../Migrating-from-SBT-0.7.x-to-0.10.x.md     |  4 ++--
 Detailed-Topics/Scripts.md                    |  2 +-
 Extending/Input-Tasks.md                      |  4 ++--
 FAQ.md                                        |  2 +-
 Getting-Started/Getting-Started-Hello.md      |  2 +-
 Getting-Started/Getting-Started-Setup.md      |  2 +-
 9 files changed, 34 insertions(+), 13 deletions(-)

diff --git a/Community/Changes.md b/Community/Changes.md
index d164f7f..993299d 100644
--- a/Community/Changes.md
+++ b/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:
diff --git a/Community/Nightly-Builds.md b/Community/Nightly-Builds.md
index 209c42d..753bafe 100644
--- a/Community/Nightly-Builds.md
+++ b/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.
diff --git a/Detailed-Topics/Launcher.md b/Detailed-Topics/Launcher.md
index aed83d7..7fad451 100644
--- a/Detailed-Topics/Launcher.md
+++ b/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
diff --git a/Detailed-Topics/Migrating-from-SBT-0.7.x-to-0.10.x.md b/Detailed-Topics/Migrating-from-SBT-0.7.x-to-0.10.x.md
index b3eea85..af5203e 100644
--- a/Detailed-Topics/Migrating-from-SBT-0.7.x-to-0.10.x.md
+++ b/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
diff --git a/Detailed-Topics/Scripts.md b/Detailed-Topics/Scripts.md
index 9f95cc2..35196be 100644
--- a/Detailed-Topics/Scripts.md
+++ b/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`.
diff --git a/Extending/Input-Tasks.md b/Extending/Input-Tasks.md
index f95a0bc..b4ce01c 100644
--- a/Extending/Input-Tasks.md
+++ b/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")
 ```
 
diff --git a/FAQ.md b/FAQ.md
index a1d7b97..1c1121d 100644
--- a/FAQ.md
+++ b/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
diff --git a/Getting-Started/Getting-Started-Hello.md b/Getting-Started/Getting-Started-Hello.md
index acb6b52..86f25ae 100644
--- a/Getting-Started/Getting-Started-Hello.md
+++ b/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,
diff --git a/Getting-Started/Getting-Started-Setup.md b/Getting-Started/Getting-Started-Setup.md
index 9b9ca0b..a5f7aa6 100644
--- a/Getting-Started/Getting-Started-Setup.md
+++ b/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