How do I force sbt to update scala-compiler.jar?

[Paul Butcher]

I'm playing with Eugene's macro-paradise compiler build, which is published as 2.11.0-SNAPSHOT. I'm trying to persuade sbt to update to the most recent snapshot with no joy - in particular after running "reboot full", I still find myself using 2.11.0-20121225-185448-74d60036f5 whereas the most recent published snapshot is 2.11.0-20121229.042200-5. This is with sbt 0.13.0-20121202-052047.

I'm sure that I can force it to update by deleting ~/.sbt and ~/.ivy2, but this is a major PITA. What do I need to do to kick sbt into updating?

Thanks in advance,

--
paul.butcher->msgCount++

Snetterton, Castle Combe, Cadwell Park...
Who says I have a one track mind?

http://www.paulbutcher.com/
LinkedIn: http://www.linkedin.com/in/paulbutcher
MSN: pa...@paulbutcher.com
AIM: paulrabutcher
Skype: paulrabutcher

[Eugene Burmako]

A clarification. The build has org.scala-lang.macro-paradise in its groupId as described here: http://docs.scala-lang.org/overviews/macros/paradise.html.

[Paul Phillips]

On Sat, Dec 29, 2012 at 9:49 AM, Paul Butcher <pa...@paulbutcher.com> wrote:

I'm sure that I can force it to update by deleting ~/.sbt and ~/.ivy2, but this is a major PITA. What do I need to do to kick sbt into updating?

It occurs to me that one could do pretty well in these matters as follows. Regardless of the resolution of this one, I'm sure similar matters will arise indefinitely.

Don't run this as-is unless you don't mind losing those directories; it's just painting the picture.

#!/usr/bin/env bash

#

mv .ivy2 .ivy2-saved

mv .sbt .sbt-saved

( cd $(mktemp -dt foo) && sbt -sbt-create <whatever options here> -v update )

rsync -av .sbt/ .sbt-saved

rsync -av .ivy2/ .ivy2-saved

rm -rf .sbt .ivy2

mv .ivy2-saved .ivy2

mv .sbt-saved .sbt

[Johannes Rudolph]

On Saturday, December 29, 2012 6:49:18 PM UTC+1, Paul Butcher wrote:

I'm sure that I can force it to update by deleting ~/.sbt and ~/.ivy2, but this is a major PITA. What do I need to do to kick sbt into updating?

Have you tried deleting just

~/.ivy2/cache/org.scala-lang.macro-paradise and ~/.sbt/boot/org.scala-lang.macro-paradise.scala-2.11.0-SNAPSHOT ?

[Paul Butcher]

On 30 Dec 2012, at 10:33, Johannes Rudolph <johannes...@gmail.com> wrote:

Have you tried deleting just

~/.ivy2/cache/org.scala-lang.macro-paradise and ~/.sbt/boot/org.scala-lang.macro-paradise.scala-2.11.0-SNAPSHOT ?

I haven't, but if the only way to get this to work is to play these kinds of games then I'll simply give up and compile scala locally. 

[Josh Suereth]

Sbt's boot cache (~/.sbt/boot/<group>) is still used to pull scala in 0.12.  *that* cache does not support snapshots, and is the one causing issues.

My recommendation is to use full-versioned nightlies or just clean out the macro-paradise boot directory and restart sbt when you need the newest version.

Note:  I think mark cleaned up sbt 0.13 so scala no longer uses the boot cache, but the regular ivy cache.

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

[Paul Butcher]

On 31 Dec 2012, at 14:33, Josh Suereth <joshua....@gmail.com> wrote:

Sbt's boot cache (~/.sbt/boot/<group>) is still used to pull scala in 0.12.  *that* cache does not support snapshots, and is the one causing issues.

My recommendation is to use full-versioned nightlies or just clean out the macro-paradise boot directory and restart sbt when you need the newest version.

Note:  I think mark cleaned up sbt 0.13 so scala no longer uses the boot cache, but the regular ivy cache.

I'm not sure that this is the case - I'm using the most recent sbt 0.13.0 snapshot  (0.13.0-20121202-052047).

[Josh Suereth]

Ah.... May still be in a branch then.   In know it's planned, but it also may be buggy.   When I'm at a computer I'll try to investigate for you.