Latest Compiler and Lib and ScalaTest: Compilation Error

On Fri, 2009-11-13 at 12:08 +0100, Philip Köster wrote:
> Is that a problem with the compiler or does it mean the latest
> compiler or lib is no longer compatible with my version of ScalaTest?

It's likely that you just need a newer ScalaTest. We're getting near to
the 2.8 beta, so all of frequently used libraries will be recompiled
with the latest Scala soon. If no-one beats me to it, I'll try specs and
configgy later today.

> A q'n to Miles Sabin (and others): How does the version of the Scala library that the Eclipse plug-in uses, namely 2.8.0.r19611.b20091113020314, correlate with the latest `scala-lang' artifacts from the snapshots repository?

As you see in the name, it's from the same nightly:

2.8.0.r19611.b20091113020314

The nightly built at 2am on Nov 13 from SVN revision 19611.

Best,
Ismael

> It's likely that you just need a newer ScalaTest. We're getting near to
> the 2.8 beta, so all of frequently used libraries will be recompiled
> with the latest Scala soon.

So a newer ScalaTest is not available yet, right? Or am I looking into the wrong repositories?

> As you see in the name, it's from the same nightly:
>
> 2.8.0.r19611.b20091113020314

That much is clear, but how does rev. # 19611 correlate with ``031119-258" from the Maven-artifact version?

Also, but that is a Maven question rather than a tools question, I don't know how to pick a specific compiler and library version from my local repository. I need to specify ``2.8.0-SNAPSHOT" as the version, which will always download and pick the latest snapshot. Sometimes I don't want this when yesterday's snapshot worked but today's doesn't ...

Cheers
---Ph.

On Fri, 2009-11-13 at 12:33 +0100, Philip Köster wrote:
> > It's likely that you just need a newer ScalaTest. We're getting near to
> > the 2.8 beta, so all of frequently used libraries will be recompiled
> > with the latest Scala soon.
>
> So a newer ScalaTest is not available yet, right? Or am I looking into the wrong repositories?

Maybe try the following:

http://scala-tools.org/repo-snapshots/org/scalatest/scalatest/1.0-for-sc...

That seems to be recompiled every day.

> > As you see in the name, it's from the same nightly:
> >
> > 2.8.0.r19611.b20091113020314
>
> That much is clear, but how does rev. # 19611 correlate with ``031119-258" from the Maven-artifact version?

Looking at the date for the snapshot should be more informative, I
believe.

Ismael

the r#X is done such that X -> the subversion version on the build.  I actually think this is very handy.

Unforuntately, we're naming nighltly builds just 2.8.0-SNAPSHOT, so..... It just appends the date and a "uid" for the snapshot in that directory.  the UID just tells you how many nightly deployments there have been for that artifact (in your case 258 nightlies), and therefore is not useful.

If you keep the dates aligned, they are built during the same nightly process, so you should be ok.

- Josh

On Fri, Nov 13, 2009 at 6:33 AM, Philip Köster <philip.koester@web.de> wrote:

> It's likely that you just need a newer ScalaTest. We're getting near to
> the 2.8 beta, so all of frequently used libraries will be recompiled
> with the latest Scala soon.

So a newer ScalaTest is not available yet, right? Or am I looking into the wrong repositories?

> As you see in the name, it's from the same nightly:
>
> 2.8.0.r19611.b20091113020314

That much is clear, but how does rev. # 19611 correlate with ``031119-258" from the Maven-artifact version?

Also, but that is a Maven question rather than a tools question, I don't know how to pick a specific compiler and library version from my local repository. I need to specify ``2.8.0-SNAPSHOT" as the version, which will always download and pick the latest snapshot. Sometimes I don't want this when yesterday's snapshot worked but today's doesn't ...

Cheers
---Ph.

> Maybe try the following:
>
> http://scala-tools.org/repo-snapshots/org/scalatest/scalatest/1.0-for-sc...

I changed my dependency to:

org.scalatest
scalatest
1.0-for-scala-2.8.0-SNAPSHOT

but still receive the same message from `scala:testCompile':

[INFO] Compiling 8 source files to D:\phrood\scarab-test\target\test-classes
error: class file needed by AssertionsForJUnit is missing.
reference type Throwable of object Predef refers to nonexisting symbol.
one error found

Nothing new was downloaded, anyway.

---Ph.

We don't build it every night. Bill is suggesting putting out a snapshot once a week. The latest scalatest snapshot was compiled against 10/26:

http://scala-tools.org/repo-snapshots/org/scalatest/scalatest/1.0-for-scala-2.8.0.20091026-SNAPSHOT/ 

I've been trying to get a new build out the door for a week, but various different things are preventing. Hopefully it will go out this today, but its likely that its the 11/06 build, which is the same one as the latest scalacheck.

Also, the next release will be 1.01, not a snapshot.

Sorry I can't give you more info.

On Fri, Nov 13, 2009 at 6:46 AM, Philip Köster <philip.koester@web.de> wrote:

> Maybe try the following:
>
> http://scala-tools.org/repo-snapshots/org/scalatest/scalatest/1.0-for-scala-2.8.0-SNAPSHOT/

I changed my dependency to:

<dependency>
       <groupId>org.scalatest</groupId>
       <artifactId>scalatest</artifactId>
       <version>1.0-for-scala-2.8.0-SNAPSHOT</version>
</dependency>

but still receive the same message from `scala:testCompile':

[INFO] Compiling 8 source files to D:\phrood\scarab-test\target\test-classes
error: class file needed by AssertionsForJUnit is missing.
reference type Throwable of object Predef refers to nonexisting symbol.
one error found

Nothing new was downloaded, anyway.

---Ph.