[ANNOUCE] sbt 1.0.1 is released

[eugene yokota]

Howdy,

I am happy to announce sbt 1.0.1, first hotfix for 1.0.0.

### Bug fixes

- Fixes command support for cross building `+` command. The `+` added to sbt 1.0 traveres over the subprojects, respecting `crossScalaVersions`; however, it no longer accepted commands as arguments. This brings back the support for it. [#3446][3446] by [@jroper][@jroper]

- Fixes `addSbtPlugin` to use the correct version of sbt during cross building. [#3442][3442] by [@dwijnand][@dwijnand]

- Fixes `run in Compile` task not including `Runtime` configuration, by reimplementing `run` in terms of `bgRun`. [#3477][3477] by [@eed3si9n][@eed3si9n]

- Shows `actual` as a potential option of `inspect` [#3335][3335] by [@Duhemm][@Duhemm]

- Includes base directory to watched sources. [#3439][3439] by [@Duhemm][@Duhemm]

- Adds an attempt to workaround intermittent `NullPointerException` arround logging. [util#121][util121] by [@eed3si9n][@eed3si9n]

- Reverts a bad forward porting. [#3481][3481] by [@eed3si9n][@eed3si9n]

### WatchSource

The watch source feature went through a major change from sbt 0.13 to sbt 1.0 using NIO; however, it did not have clear migration path, so we are rectifying that in sbt 1.0.1.

First, `sbt.WatchSource` is a new alias for `sbt.internal.io.Source`. Hopefully this is easy enough to remember because the key is named `watchSources`. Next, `def apply(base: File)` and `def apply(base: File, includeFilter: FileFilter, excludeFilter: FileFilter)` constructors were added to the companion object of `sbt.WatchSource`.

For backward compatiblity, sbt 1.0.1 adds `+=` support (`Append` instance) from `File` to `Seq[WatchSource]`.

So, if you have a directory you want to watch:

    watchSources += WatchSource(sourceDirectory.value)

If you have a list of files:

    watchSources ++= (sourceDirectory.value ** "*.scala").get

[#3438][3438] by [@Duhemm][@Duhemm]; [#3478][3478] and [io#74][io74] by [@eed3si9n][@eed3si9n]

sbt team

[Kevin Tham]

Great! Will the artifacts be posted to https://github.com/sbt/sbt/releases soon also?

[eugene yokota]

Hopefully yes.

-eugene

[Kevin Tham]

Just wondering, is this a manually triggered process? Looks like the artifacts are still not up on Github releases page

[eugene yokota]

We are in the process of switching to another CDN.

Could you grab the release from the links on http://www.scala-sbt.org/download.html?

-eugene

--
You received this message because you are subscribed to the Google Groups "sbt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sbt-dev+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sbt-dev/5b40686d-0068-4a88-b448-75ec692edad9%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Kevin Tham]

I see, got it, thanks!

Is it reasonable to assume in my scripts that future releases be based off of this url structure: https://cocl.us/sbt-<version>.tgz?

To unsubscribe from this group and stop receiving emails from it, send an email to sbt-dev+u...@googlegroups.com.

[eugene yokota]

Probably.

-eugene

To unsubscribe from this group and stop receiving emails from it, send an email to sbt-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sbt-dev/aeff5ab9-aeef-4154-81db-73243592d181%40googlegroups.com.