summaryrefslogtreecommitdiff
path: root/lib/scala-compiler-src.jar.desired.sha1
diff options
context:
space:
mode:
authorEugene Burmako <xeno.by@gmail.com>2012-08-01 19:58:47 +0200
committerEugene Burmako <xeno.by@gmail.com>2012-08-02 15:51:26 +0200
commita19f0e83bf18a435bac9c984781f66ac3d94822c (patch)
tree967ea357afd0fb01e58e0da0a9bb4df395c1e291 /lib/scala-compiler-src.jar.desired.sha1
parentf7164b871530a68b100d540b876187036c1c6cbc (diff)
downloadscala-a19f0e83bf18a435bac9c984781f66ac3d94822c.tar.gz
scala-a19f0e83bf18a435bac9c984781f66ac3d94822c.tar.bz2
scala-a19f0e83bf18a435bac9c984781f66ac3d94822c.zip
deploys a new starr that knows reify is a macro
reify has just been moved to base.Universe from api.Universe, so the fast track in the old starr doesn't know about its existence. Therefore locker is built without reify having the MACRO flag, thus it won't be able to expand reify. Strictly speaking we don't need a new starr, because reify isn't used in scalac so, even though locker won't recognize reify, quick will be fine. However you don't know where a little sloppiness is going to bite you, so I took time to rebuild and push the new starr. It was as simple as "ant build starr.done" of the parent commit. No file mingling was required.
Diffstat (limited to 'lib/scala-compiler-src.jar.desired.sha1')
-rw-r--r--lib/scala-compiler-src.jar.desired.sha12
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/scala-compiler-src.jar.desired.sha1 b/lib/scala-compiler-src.jar.desired.sha1
index de9d23e095..95973402e6 100644
--- a/lib/scala-compiler-src.jar.desired.sha1
+++ b/lib/scala-compiler-src.jar.desired.sha1
@@ -1 +1 @@
-a347985ce7eeb0fa4d595ec3b8d1ce5de7373a51 ?scala-compiler-src.jar
+67257bb7ce010e2ceac800d737e202cfbfc2a1f6 ?scala-compiler-src.jar