Re: [sbt] Windows .msi for 0.12?

[Josh Suereth]

The docs are stale, the release is here: http://repo.scala-sbt.org/scalasbt/sbt-native-packages/org/scala-sbt/sbt/0.12.2/sbt.msi

On Feb 13, 2013 4:25 AM, <rkl...@gmail.com> wrote:

Hi all,

I have created a large project using lots of subprojects using sbt. I did not have any problems that I could not solve by reading the getting started guide. I like it very much so far.

However, one of the main reasons I decided to try out sbt (before we were just building from inside intellij IDEA) was the ability to painlessly switch libraries like the scala version for all subprojects without having to click through a million modal dialogs.

I noticed that the .msi available from the setup page http://www.scala-sbt.org/release/docs/Getting-Started/Setup.html is 0.11.3. Also, the sbt version that is included in the typesafe stack is 0.11.3. But I could not get 0.11.3 to work with scala 2.10. Uninstalling the typesafe stack on my local machine and installing the standalone .deb gave me sbt version 0.12.0, which works with scala 2.10.

But my colleagues are using windows. Is there a windows .msi available for a current version of sbt like 0.12.0? Alternatively, will the typesafe stack be upgraded to scala 2.10 soon? If not, what is the recommended way to use scala 2.10 from windows?

best regards,

Rüdiger

--
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.
 
 

[Mark Harrah]

On Wed, 13 Feb 2013 08:00:32 -0500
Josh Suereth <joshua....@gmail.com> wrote:

> The docs are stale, the release is here:
> http://repo.scala-sbt.org/scalasbt/sbt-native-packages/org/scala-sbt/sbt/0.12.2/sbt.msi

I'm pretty sure that's the same file as is linked to in the docs. The doc link is:

http://scalasbt.artifactoryonline.com/scalasbt/sbt-native-packages/org/scala-sbt/sbt//0.12.2/sbt.msi

There's a redundant slash and the hostname is the direct one, but the content hashes to the same value.

-Mark

[Josh Suereth]

Hmm.... This is the one I'm using.   I wonder if it bundled 0.11.3-2 launcher...,

Can you check if sbt.version is set in your project/build.properties file?

[rkl...@gmail.com]

Thanks.

I uninstalled the old sbt.msi and installed the new one from the location below. According to diff it is the same as the one from the docs.

But I still get 0.11.3 when I enter "sbt sbt-version", even when I go to a directory without any project, like my home directory. I even deleted my ~/.sbt directory to make sure it is a clean install.

Am I doing something wrong?

C:\Users\rklaehn>sbt sbt-version
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[info] Loading project definition from C:\Users\rklaehn\.sbt
[info] Set current project to default-4ed8a9 (in build file:/C:/Users/rklaehn/)
[info] 0.11.3

[rkl...@gmail.com]

I did not have a project/build.properties file. I now added one and put sbt.version=0.12.0 in it, and now everything seems to work on windows. However, if I enter sbt sbt-version in a non-project directory I still get 0.11.3.

Is this the recommended way to use sbt 0.12? I was expecting that he would default to 0.12. It's all a bit confusing. 

Anyway, thanks for your help,

Rüdiger

[Josh Suereth]

No, I think my packaging process is using stale launchers.  So that's the 0.11.3-2 launcher packaged with the 0.12.2 script updates.

Since the launcher is so stable, its mostly a non-issue.   I'll work on fixing the build and updating the release process for sbt.

[Brian Smith]

Hi

The launch jar in the 0.12.2 msi is definitely the 0.11.3-2 one - I checked the manifest and checksum.

It's not a big deal, but this was completely stopping me from getting a proxy repository to work following the instructions here:

http://www.scala-sbt.org/release/docs/Detailed-Topics/Proxy-Repositories.html#sbt-repository-config

No matter what I did, override-build-resolvers remained false.  

I was able to resolve it by replacing the launch jar with this one:

http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.12.2/sbt-launch.jar

If I hadn't vaguely remembered skimming this thread I'd never have made the connection!

I mention this in case someone else runs into the same or there are any other new features reliant on launcher changes.

Thanks

Brian

[rkl...@gmail.com]

I would argue that if you have to manually install a jar to get something to work, it is a big deal. The whole point of having an .msi or .deb is to not have to do something like this.

But I assume that it fill be fixed soon.

[Josh Suereth]

This is fixed now if you download the MSI on the download page.

SOrry for the issues!

[Mark Harrah]

On Fri, 22 Feb 2013 10:29:18 -0500
Josh Suereth <joshua....@gmail.com> wrote:

> This is fixed now if you download the MSI on the download page.

Thanks, Josh! Is this also fixed: https://github.com/sbt/sbt/issues/662 ?

-Mark

> SOrry for the issues!
>
>
> On Sun, Feb 17, 2013 at 4:05 AM, <rkl...@gmail.com> wrote:
>
> > I would argue that if you have to manually install a jar to get something
> > to work, it is a big deal. The whole point of having an .msi or .deb is to
> > not have to do something like this.
> >
> > But I assume that it fill be fixed soon.
> >
> > Am Sonntag, 17. Februar 2013 01:43:25 UTC+1 schrieb Brian:
> >>
> >> Hi
> >>
> >> The launch jar in the 0.12.2 msi is definitely the 0.11.3-2 one - I
> >> checked the manifest and checksum.
> >>
> >> It's not a big deal, but this was completely stopping me from getting a
> >> proxy repository to work following the instructions here:
> >>

> >> http://www.scala-sbt.org/**release/docs/Detailed-Topics/**
> >> Proxy-Repositories.html#sbt-**repository-config<http://www.scala-sbt.org/release/docs/Detailed-Topics/Proxy-Repositories.html#sbt-repository-config>

> >>
> >> No matter what I did, override-build-resolvers remained false.
> >>
> >> I was able to resolve it by replacing the launch jar with this one:
> >>

> >> http://repo.typesafe.com/**typesafe/ivy-releases/org.**
> >> scala-sbt/sbt-launch/0.12.2/**sbt-launch.jar<http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.12.2/sbt-launch.jar>

> >>>>>> > http://repo.scala-sbt.org/**scal**asbt/sbt-native-packages/**org/**
> >>>>>> scala-sbt/sbt/0.12.2/sbt.**msi<http://repo.scala-sbt.org/scalasbt/sbt-native-packages/org/scala-sbt/sbt/0.12.2/sbt.msi>

> >>>>>>
> >>>>>> I'm pretty sure that's the same file as is linked to in the docs.
> >>>>>> The doc link is:
> >>>>>>

> >>>>>> http://scalasbt.**artifactoryonl**ine.com/**scalasbt/sbt-native-**
> >>>>>> packages/**org/scala-sbt/sbt//0.**12.2/sbt.**msi<http://scalasbt.artifactoryonline.com/scalasbt/sbt-native-packages/org/scala-sbt/sbt//0.12.2/sbt.msi>

> >>>>>>
> >>>>>> There's a redundant slash and the hostname is the direct one, but the
> >>>>>> content hashes to the same value.
> >>>>>>
> >>>>>> -Mark
> >>>>>>
> >>>>>> > On Feb 13, 2013 4:25 AM, <rkl...@gmail.com> wrote:
> >>>>>> >
> >>>>>> > > Hi all,
> >>>>>> > >
> >>>>>> > > I have created a large project using lots of subprojects using
> >>>>>> sbt. I did
> >>>>>> > > not have any problems that I could not solve by reading the
> >>>>>> getting started
> >>>>>> > > guide. I like it very much so far.
> >>>>>> > >
> >>>>>> > > However, one of the main reasons I decided to try out sbt (before
> >>>>>> we were
> >>>>>> > > just building from inside intellij IDEA) was the ability to
> >>>>>> painlessly
> >>>>>> > > switch libraries like the scala version for all subprojects
> >>>>>> without having
> >>>>>> > > to click through a million modal dialogs.
> >>>>>> > >
> >>>>>> > > I noticed that the .msi available from the setup page

> >>>>>> > > http://www.scala-sbt.org/**relea**se/docs/Getting-Started/**
> >>>>>> Setup.**html<http://www.scala-sbt.org/release/docs/Getting-Started/Setup.html>is