Re: Latest Compiler and Lib and ScalaTest: Compilation Error

scala-tools.org is not EPFL.

scala-tools is working on automatically making snapshots of ScalaCheck (and other projects) for various jvm versions against the nightlies.  When I find more time, hopefully I can progress more on this.  In the meantime, it's up to the discretion of the projects how often/when they post releases.


- Josh

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

Josh Cough wrote:

> We don't build it every night.

Isn't it so that you already use the EPFL infrastructure? I don't know how the build is organized and am really just guessing this from the fact that the ScalaTest artifact resides on `http://scala-tools.org/repo-snapshots'. If that's true, couldn't ScalaTest (and ScalaCheck) simply be added to the nightly-build Hudson procedure?

For the time being, I'm now looking for a work-around. What can I do to avoid this compilation error? Go back to an older version of `scala-library' and `scala-compiler'? How? I don't know how to do it, Maven-wise. I can pass ``2.8.0-20090801.003617-189" as the artifact version for instance, which Maven will then download but apparently not use in favor of the latest snapshot found in the repository.

The only ``work-around" I found so far is to completely remove the unit test using ScalaTest, which is of course not very satisfactory.

Best
---Phil

> scala-tools.org is not EPFL.
>
> scala-tools is working on automatically making snapshots of
> ScalaCheck (and other projects) for various jvm versions against the
> nightlies. When I find more time, hopefully I can progress more on
> this. In the meantime, it's up to the discretion of the projects how
> often/when they post releases.

Okay, thanks for these updates. So is anyone using the latest compiler and library snapshots with ScalaTest? I can't get it to compile and would like to know how others do it. I'm stuck here.

---Phil

I was just able to build it against scala 11/06. I tried to publish the snapshot but, I'm having issues with that. Not sure why. If it helps, I could send people the jar directly.

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

> scala-tools.org is not EPFL.
>
> scala-tools is working on automatically making snapshots of
> ScalaCheck (and other projects) for various jvm versions against the
> nightlies. When I find more time, hopefully I can progress more on
> this. In the meantime, it's up to the discretion of the projects how
> often/when they post releases.

Okay, thanks for these updates. So is anyone using the latest compiler and library snapshots with ScalaTest? I can't get it to compile and would like to know how others do it. I'm stuck here.

---Phil

> I was just able to build it against scala 11/06. I tried to publish the
> snapshot but, I'm having issues with that. Not sure why. If it helps, I
> could send people the jar directly.

Thanks for this friendly offer, Josh. If you could send the jar along
with its sources, I'd happily take it.

But the whole situation is not very comfortable. Every morning I
download a new Scala snapshot, which I can't really avoid to do, I might
run into compile/link problems. Pretty everything scalaish I'm using is
bleeding-edge, and I find myself contemplating about version numbers for
more than it is wonderful. This is not to nag at anyone---only, as I
said, I don't feel comfortable with this situation.

I'd like to use Scala in a production environment, but I don't think I
could recommend that in the next few months.

Best
---Phil

PS: Good work, this ScalaTest thingy! I'll check out ScalaCheck soon,
but that's from different authors, right?

On Fri, 2009-11-13 at 18:38 +0100, Philip Köster wrote:
> But the whole situation is not very comfortable. Every morning I
> download a new Scala snapshot, which I can't really avoid to do, I might
> run into compile/link problems. Pretty everything scalaish I'm using is
> bleeding-edge, and I find myself contemplating about version numbers for
> more than it is wonderful. This is not to nag at anyone---only, as I
> said, I don't feel comfortable with this situation.
>
> I'd like to use Scala in a production environment, but I don't think I
> could recommend that in the next few months.

Well, many of us are using Scala 2.7.x in production without any issues
when it comes to versions. Using Scala trunk for production is not
something that should be recommended indeed.

Best,
Ismael

> Well, many of us are using Scala 2.7.x in production without any issues
> when it comes to versions. Using Scala trunk for production is not
> something that should be recommended indeed.

I wasn't even able to install Miles's 2.7.x SDT into Eclipse 3.5. How
did you do it? But anyway that's all water down the bridge now---I have
gotten used to the latest SDT and parts of the latest libs so much that
I don't want to learn 2.7.x. What I'm actually doing is research on
behalf of my own, so I think it is okay to go cutting edge this time.
But I know why I have always avoid to do this, now more than ever ...

Cheers
---Philip

Hi All,

On Fri, Nov 13, 2009 at 9:52 AM, Ismael Juma wrote:
> On Fri, 2009-11-13 at 18:38 +0100, Philip Köster wrote:
>> But the whole situation is not very comfortable. Every morning I
>> download a new Scala snapshot, which I can't really avoid to do, I might
>> run into compile/link problems. Pretty everything scalaish I'm using is
>> bleeding-edge, and I find myself contemplating about version numbers for
>> more than it is wonderful. This is not to nag at anyone---only, as I
>> said, I don't feel comfortable with this situation.
>>
>> I'd like to use Scala in a production environment, but I don't think I
>> could recommend that in the next few months.
>
> Well, many of us are using Scala 2.7.x in production without any issues
> when it comes to versions. Using Scala trunk for production is not
> something that should be recommended indeed.
>
I'd agree with that. If you're using 2.8, you're on the bleeding edge
and unfortunately need to be prepared do deal with frustrations like
this. 2.8 hasn't even been released as a release candidate yet. That
said, we've been working to get a new version of ScalaTest out the
door this week, and it has taken a few days longer than expected.
Sorry for that delay. I need to get it out today, though, because I'm
leaving for Devoxx tomorrow. We aim to deploy a 1.0.1 release with
minor bug fixes and enhancements, both for 2.7.x and 2.8-SNAPSHOT.

Thanks.

Bill
----
Bill Venners
Artima, Inc.
http://www.artima.com

There's always the free IntelliJ version.  I've made the switch myself for production code.  There's some interesting editor issues where some things compile on the command-line but not in the editor, but it works great.  I would highly recommend it.  Those of us still using scala + eclipse in production at my company are still on eclipse 3.4


- Josh

On Fri, Nov 13, 2009 at 12:59 PM, Philip Köster <philip.koester@web.de> wrote:

Well, many of us are using Scala 2.7.x in production without any issues
when it comes to versions. Using Scala trunk for production is not
something that should be recommended indeed.

I wasn't even able to install Miles's 2.7.x SDT into Eclipse 3.5. How did you do it? But anyway that's all water down the bridge now---I have gotten used to the latest SDT and parts of the latest libs so much that I don't want to learn 2.7.x. What I'm actually doing is research on behalf of my own, so I think it is okay to go cutting edge this time. But I know why I have always avoid to do this, now more than ever ...

Cheers
---Philip

On Fri, 2009-11-13 at 18:59 +0100, Philip Köster wrote:
> > Well, many of us are using Scala 2.7.x in production without any issues
> > when it comes to versions. Using Scala trunk for production is not
> > something that should be recommended indeed.
>
> I wasn't even able to install Miles's 2.7.x SDT into Eclipse 3.5. How
> did you do it?

I just installed it as any other plugin.

> But anyway that's all water down the bridge now---I have
> gotten used to the latest SDT and parts of the latest libs so much that
> I don't want to learn 2.7.x. What I'm actually doing is research on
> behalf of my own, so I think it is okay to go cutting edge this time.
> But I know why I have always avoid to do this, now more than ever ...

Right, that's perfectly fine. I just wanted to clarify it as your
previous message made it sound like there was no alternative and there
is. Not appropriate for you, but appropriate for many people.

By the way, the first 2.8.0 beta candidate was released today, so the
pain should become smaller from now on.

Best,
Ismael