API type mismatch -- what do I do?

[Daniel Sobral]

I'm trying to run something using a trunk version of Scala, and I get
these errors:

[info] 'compiler-interface' not yet compiled for Scala
2.10.0.rdev-4142-2012-01-09-gaf4a529. Compiling...
/tmp/sbt_fa5ae08e/API.scala:263: error: type mismatch;
found : API.this.global.tpnme.NameType
(which expands to) API.this.global.TypeName
required: String
sym.isLocalClass || sym.isAnonymousClass || sym.fullName.endsWith(LocalChild)

^

What do I do?

--
Daniel C. Sobral

I travel to the future all the time.

[Paul Phillips]

On Mon, Jan 9, 2012 at 8:30 AM, Daniel Sobral <dcso...@gmail.com> wrote:

What do I do?

You're screwed, as are we all.  I guess I'll put back the implicit it's depending upon until it's updated not to need it.  This is a bummer way to develop. (And a good example of why I don't want all that compiler code in sbt.)

[Miles Sabin]

I'm still seeing this with 2.10.0.rdev-4179-2012-01-15-g3024efc ...
did the implicit not go back in or has it broken again?

Cheers,

Miles

--
Miles Sabin
tel: +44 7813 944 528
gtalk: mi...@milessabin.com
skype: milessabin
g+: http://www.milessabin.com
http://twitter.com/milessabin
http://www.chuusai.com/

[Miles Sabin]

On Sun, Jan 15, 2012 at 11:49 AM, Miles Sabin <mi...@milessabin.com> wrote:
> On Tue, Jan 10, 2012 at 6:50 AM, Paul Phillips <pa...@improving.org> wrote:
>> On Mon, Jan 9, 2012 at 8:30 AM, Daniel Sobral <dcso...@gmail.com> wrote:
>>>
>>> What do I do?
>>
>> You're screwed, as are we all.  I guess I'll put back the implicit it's
>> depending upon until it's updated not to need it.  This is a bummer way to
>> develop. (And a good example of why I don't want all that compiler code in
>> sbt.)
>
> I'm still seeing this with 2.10.0.rdev-4179-2012-01-15-g3024efc ...
> did the implicit not go back in or has it broken again?

I could be missing something obvious, but this seems to be quite
difficult to fix on the SBT side.

I can replace LocalChild with LocalChild.toString (which should be
source compatible between recent 2.10.0-SNAPSHOT and earlier
revisions), but I'm still not able to build the compiler interface,
because building with it 2.10.0-SNAPSHOT requires the 2.10.0-SNAPSHOT
compiler interface to be already built ... ie. a classic bootstrapping
problem.

Any suggestions?

[Paul Phillips]

As you probably know, this is only showing up now, and has been largely overtaken by events, but I didn't have any trouble back then rebuilding sbt and then using that with trunk.

 - I made the change to sbt

 - sbt build-all publishes a new 0.11.3-SNAPSHOT

 - and then sbt -sbt-snapshot (using sbt-extras)

But further details are no longer with me lo these five days later.

[Josh Suereth]

Grzegorz posted a script onto scala-user or scala-internals with a hack to fix just the compiler-internals project of sbt 0.11.2 IIRC.   It's a nifty option for those of us who don't like using snapshot releases.

Mark had grander plans for 0.12.x (inlcuding binary compatible SBT releases), but I have no idea when we'll see a release.

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

[Miles Sabin]

On Fri, Jan 20, 2012 at 1:59 PM, Paul Phillips <pa...@improving.org> wrote:
> As you probably know, this is only showing up now, and has been largely
> overtaken by events, but I didn't have any trouble back then rebuilding sbt
> and then using that with trunk.
>
>  - I made the change to sbt
>  - sbt build-all publishes a new 0.11.3-SNAPSHOT
>  - and then sbt -sbt-snapshot (using sbt-extras)
>
> But further details are no longer with me lo these five days later.

Yes, the change I tried did actually fix things for me. What I fumbled
was the local publishing step, so my build was still picking up the
unmodified 0.11.2.

[Jason Zaugg]

By the way, if you want to use a bleeding edge version of SBT and take a punt that it will be backwards-compatible enough for existing plugins, add the following to ./project/plugins.sbt.

  sbtVersion in update := "0.11.2"

-jason

[Dave]

Does anyone know what to do in case
.sbt/boot/scala-2.9.1/org.scala-tools.sbt/sbt/0.11.2/compiler-
interface-src/compiler-interface-src-0.11.2.jar
is lost?

[Grzegorz Kossakowski]

On Friday, January 20, 2012 7:52:09 PM UTC+1, Dave wrote:

Does anyone know what to do in case
.sbt/boot/scala-2.9.1/org.scala-tools.sbt/sbt/0.11.2/compiler-
interface-src/compiler-interface-src-0.11.2.jar
is lost?

What do you mean by lost?

-- 

Grzegorz

[Paul Phillips]

On Fri, Jan 20, 2012 at 11:10 AM, Grzegorz Kossakowski <grzegorz.k...@gmail.com> wrote:

What do you mean by lost?

This is how I feel in these situations: 

 

[Dave]

Never mind .
I renamed .sbt to .sbt.old and then sbt created everything new.
I was looking for a keyword in sbt to repair .sbt if something was
deleted.

So the script didn't work on cygwin.
I did the fix manually and then it all compiles in sbt.

On 20 jan, 20:15, Paul Phillips <pa...@improving.org> wrote:
> On Fri, Jan 20, 2012 at 11:10 AM, Grzegorz Kossakowski <
>

>  lost.jpg
> 311KWeergevenDownloaden