0.13.0-Beta2

[Mark Harrah]

0.13.0-Beta2 is now available. If you are a plugin author or are
comfortable with using pre-releases, this is the release to try out.
Please publish your plugins against Beta2 to help test this release
and to help others test it. See below for details on publishing
plugins.

General information
-------------------

* See the Changes page[1] for the features in 0.13.
* Please only use the 0.13.0-Beta2 launcher[2] with 0.13.0-Beta2. This is
to avoid unnecessary complications until 0.13 goes final.
* sbt 0.13 is NOT binary compatible with 0.12. Plugins will need
to be recompiled before they can be used. Beta releases will
not be compatible with each other or with RCs.
* Known incompatibilities are collected on the wiki[3]. Please report
anything you have to do to make a 0.12 plugin or build work with 0.13.
* Many commits from 0.13 were backported to 0.12.x so that 0.13 is
mainly a feature release. See also the commit history[4].
* There won't be any native packages until the first release candidate.

Timeline
--------

1. If major issues are reported, there will likely be another Beta.
2. RC1 will be released no sooner than two weeks after this Beta (Beta2).
3. RC1 will be built against 2.10.2 final (so, no RC1 before 2.10.2 final)

Plugins
-------

sbt 0.12.4-RC2 has been published with a primary goal of making it easier
for you to publish plugins for 0.13. Specifically, you can still use sbt
0.12 (at least 0.12.4-RC2) and any 0.12 plugins for your build:

1. Get the 0.12.4-RC2 launcher
2. Set sbt.version=0.12.4-RC2 in project/build.properties
3. Change these settings in your build:

sbtVersion in Global := "0.13.0-Beta2"

scalaVersion in Global := "2.10.2-RC2"

Please post here if you have any issues building your plugin with 0.13
or if there are problems with these instructions.

Finally, please post on this thread once your plugin has been successfully
published against 0.13 and include the addSbtPlugin(...) line that will
enable it in a user's project/plugins.sbt.

Thanks,
Mark

[1] http://www.scala-sbt.org/0.13.0/docs/Community/ChangeSummary_0.13.0.html
[2] http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.13.0-Beta2/sbt-launch.jar
[3] https://github.com/sbt/sbt/wiki/0.13-Known-Issues
[4] https://github.com/sbt/sbt/commits/v0.13.0-Beta2

[Josh Suereth]

This plugin bit is great news!  Looks like my evening/morning will be a bit busy trying out Beta2.

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simple-build-t...@googlegroups.com.
To post to this group, send email to simple-b...@googlegroups.com.
Visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Paul Phillips]

On Thu, Jun 6, 2013 at 9:22 AM, Mark Harrah <dmha...@gmail.com> wrote:

0.13.0-Beta2 is now available.  

1) It chastises me every time it starts about "Unable to bind key for unsupported operation: magic-space" Yes I'm sure it seems "magical" to you, jline, but .inputrc is primarily intended for real readline, not its java knockoffs. jline being all pedantic about the contents of the file is not appropriate, given that jline is an usurper.

2) Apparently there are rules about how I name my project directory. Is this necessary?

% mkdir 23skidoo && cd 23skidoo

% java -jar ~/.sbt/launchers/0.13.0-Beta2/sbt-launch.jar update

[error] Invalid project ID: Expected letter

[error] 23skidoo

[error] ^

[error] Use 'last' for the full log.

[INFO] Unable to bind key for unsupported operation: magic-space

[Heiko Seeberger]

On Jun 7, 2013, at 12:58 AM, Paul Phillips <pa...@improving.org> wrote:

2) Apparently there are rules about how I name my project directory. Is this necessary?

% mkdir 23skidoo && cd 23skidoo

% java -jar ~/.sbt/launchers/0.13.0-Beta2/sbt-launch.jar update

[error] Invalid project ID: Expected letter

[error] 23skidoo

[error] ^

[error] Use 'last' for the full log.

[INFO] Unable to bind key for unsupported operation: magic-space

Ran into the same one. But I'm subservient to authority and silently accepted my fault.

Heiko

[Mark Harrah]

On Thu, 6 Jun 2013 15:58:34 -0700
Paul Phillips <pa...@improving.org> wrote:

> On Thu, Jun 6, 2013 at 9:22 AM, Mark Harrah <dmha...@gmail.com> wrote:
>
> > 0.13.0-Beta2 is now available.
>
>
> 1) It chastises me every time it starts about "Unable to bind key for
> unsupported operation: magic-space" Yes I'm sure it seems "magical" to you,
> jline, but .inputrc is primarily intended for real readline, not its java
> knockoffs. jline being all pedantic about the contents of the file is not
> appropriate, given that jline is an usurper.

According to [1] you can change the location used by jline with a system property or a ~/.jlinerc file.

> 2) Apparently there are rules about how I name my project directory. Is
> this necessary?
>
> % mkdir 23skidoo && cd 23skidoo
> % java -jar ~/.sbt/launchers/0.13.0-Beta2/sbt-launch.jar update
> [error] Invalid project ID: Expected letter
> [error] 23skidoo
> [error] ^
> [error] Use 'last' for the full log.
> [INFO] Unable to bind key for unsupported operation: magic-space

0.13 will use the project directory name as the project ID unless you explicitly define a project for the root directory, such as:

lazy val myprojectid = project in file(".")

It does make an attempt to normalize the directory name, but it doesn't handle all situations. In this case, it would need to either drop the initial numbers or add a letter so that it starts with a letter. Some possible improvements:

* check the project ID earlier and indicate that the directory name is an invalid project ID
* suggest defining the root project explicitly
* automatically prepend "root-" or something along those lines
* use some other default ID, like was done previously
* possibly allow an ID to start with a number- I'm not sure this is possible, so I'd have to check into it

Thanks for the feedback.

-Mark

[1] https://github.com/jline/jline2/wiki/Configuration-Properties

[Paul Phillips]

On Thu, Jun 6, 2013 at 4:19 PM, Mark Harrah <dmha...@gmail.com> wrote:

According to [1] you can change the location used by jline with a system property or a ~/.jlinerc file.

In case it's a matter of general interest, it's -Djline.inputrc you have to set to change it via system property. I didn't exactly relish having to supply this property on every invocation for the rest of my life, so for others who encounter this, here is the incantation to silence it:

echo 'jline.inputrc=$HOME/.jline-inputrc' > ~/.jline.rc

touch ~/.jline-inputrc

This of course replaces my 56 line .inputrc with a 0 line .jline-inputrc, which is somewhat undesirable, but seeing as I don't even know what settings jline honors, it's not as undesirable as having two config files which are identical but for one line.

[Paul Phillips]

Aha, I am pleased to find there is a real solution to this. For my cynicism this is a difficult blow.

$if Bash
   Space: magic-space
 $endif

That's what you want in your ~/.inputrc, no further tweaks required.

[Mikko Peltonen]

Sbt-idea published for 0.13.0-Beta2. Put this into project/plugins.sbt to use with Beta2:

resolvers += "Sonatype snapshots" at "http://oss.sonatype.org/content/repositories/snapshots/"

addSbtPlugin("com.github.mpeltonen" % "sbt-idea" % "1.5.0-SNAPSHOT") 

Br,

Mikko

[eugene yokota]

Back published:

- sbt-assembly 0.9.0

- sbt-buildinfo 0.2.5

- sbt-dirty-money 0.0.1

- sbt-scalashim 0.2.2

- sbt-man 0.1.0

- sbt-uniqueversion 0.1.0

- sbt-unidoc 0.1.2

for sbt 0.13.0-Beta 2.

I used sbt 0.12.4-RC2 cross building for most of them.

It'd be nice if I could run scripted in there too: 

java.lang.NoSuchMethodError: scala.Predef$.augmentString(Ljava/lang/String;)Lscala/collection/immutable/StringOps

-eugene

[Mark Harrah]

Not sure if it's fixable, but please open an issue and I'll look at it.

-Mark

[Mark Harrah]

Ok, I think I almost fixed it. The terminal gets messed up, but I
guess that is just the two JLines fighting. Please still open an
issue to track it though.

-Mark

[eugene yokota]

Opened: https://github.com/sbt/sbt/issues/781

-eugene

[Josh Suereth]

I just back published published:

sbt-pgp 0.8,

sbt-git 0.5.0

sbt-site 0.6.2

sbt-ghpages 0.5.1

To be continued with the sbt-native packager.

[Doug Tangren]

On Jun 10, 2013 2:19 PM, "Josh Suereth" <joshua....@gmail.com> wrote:
>
> I just back published published:
>
> sbt-pgp 0.8,
> sbt-git 0.5.0
> sbt-site 0.6.2
> sbt-ghpages 0.5.1
>
> To be continued with the sbt-native packager.
>

Working on publishing at scaladays and ran into an issue with the launcher. I upgraded my scala version to publish a plugin and also wanted to update a conscript app which inits a project with the plugin installed. I noticed that in specifying the scala version in my launch config it expects a full version to resolve the scala std lib but it expects a binary version to resolve my library. Heres and example https://github.com/softprops/ls/blob/master/src/main/conscript/lsinit/launchconfig

Mark if you see me at scaladays come grab me. Otherwise I'm come looking for you

[Doug Tangren]

On Tue, Jun 11, 2013 at 12:20 PM, Doug Tangren <d.ta...@gmail.com> wrote:

On Jun 10, 2013 2:19 PM, "Josh Suereth" <joshua....@gmail.com> wrote:
>
> I just back published published:
>
> sbt-pgp 0.8,
> sbt-git 0.5.0
> sbt-site 0.6.2
> sbt-ghpages 0.5.1
>
> To be continued with the sbt-native packager.
>

Working on publishing at scaladays and ran into an issue with the launcher. I upgraded my scala version to publish a plugin and also wanted to update a conscript app which inits a project with the plugin installed. I noticed that in specifying the scala version in my launch config it expects a full version to resolve the scala std lib but it expects a binary version to resolve my library. Heres and example https://github.com/softprops/ls/blob/master/src/main/conscript/lsinit/launchconfig

Mark if you see me at scaladays come grab me. Otherwise I'm come looking for you

Figured it out ( with the help of eugene z ). I just had to specify cross-versioned: false and the specific cross-versioned name of my library then use the full version for scala.

[eugene yokota]

I sent in a pull req for this and 0.13 shouldn't have this problem: https://github.com/sbt/sbt/pull/655

> ### what this changes

>

> 1. `cross-versioned` property is expanded to `true|false|none|binary|full`.

> 2. `cross-versioned` now defaults to `binary`.

> 3. when `cross-versioned` is `binary` it uses `LaunchCrossVersion.binaryScalaVersion(sv)` to build the _2.10 style suffix.

-eugene

[Heiko Seeberger]

On Jun 9, 2013, at 1:16 PM, Mikko Peltonen <mikko.j....@gmail.com> wrote:

resolvers += "Sonatype snapshots" at "http://oss.sonatype.org/content/repositories/snapshots/"

You can use 

resolvers += Opts.resolver.sonatypeSnapshots

Heiko

[Doug Tangren]

back-published

addSbtPlugin("me.lessis" % "ls-sbt" % "0.1.2")

addSbtPlugin("me.lessis" % "jot" % "0.1.0")

addSbtPlugin("me.lessis" % "less-sbt" % "0.1.10")

addSbtPlugin("me.lessis" % "coffeescripted-sbt" % "0.2.3")

addSbtPlugin("me.lessis" % "sbt-growl-plugin" % "0.1.3")

Didn't see any real issues. Mostly things moved from the Project namespace to the Def namespace. Easy Peazy

-Doug Tangren
http://lessis.me

[Josh Suereth]

Just published sbteclipse 2.2.0 for sbt 0.13.0-Beta2.  Seems to work excellently.

[Heiko Seeberger]

On Jun 18, 2013, at 5:12 PM, Josh Suereth <joshua....@gmail.com> wrote:

Just published sbteclipse 2.2.0 for sbt 0.13.0-Beta2.  Seems to work excellently.

It has to, because you are giving so much love to it ;-)

Heiko

Visit this group at http://groups.google.com/group/simple-build-tool.

[David Pérez]

I think my problem with SBT 0.13.7 is related with this thread:

http://stackoverflow.com/questions/27823977/noise-logging-for-each-command-i-issue-in-sbt

Any help will be appreciated.

   David

[Josh Suereth]

did you try the following?

echo 'jline.inputrc=$HOME/.jline-inputrc' > ~/.jline.rc

touch ~/.jline-inputrc

--

You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simple-build-t...@googlegroups.com.
To post to this group, send email to simple-b...@googlegroups.com.
Visit this group at http://groups.google.com/group/simple-build-tool.

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