continuing failure of ScalaTest + 2.8 under IntelliJ

On Friday July 9 2010, Kevin Wright wrote:
> looks like this issue:
>
> http://youtrack.jetbrains.net/issue/SCL-2048?query=ScalaTest09Scala28
>Runner is still present in the latest build of the IDEA/Scala plugin
> for 9.0.2
>
> It's been present from at least 2..0.RC3 through to the present
> 2.8.0.RC7
>
> Maia is not an option for me, I use the IDE heavily for my day job
> (including some small pieces of Scala) and it absolutely must be
> stable. If I update to the latest scala plugin when running under
> Maia then it stops working under 9.0.2

Maia _is_ IDEA 9.

JetBrains EAPs for IDEA are entirely stable enough for
everyday "real-world" or "professional" use. Only early in the
development of a new major release is this not generally true. It is
rare for the EAP of a point release to be at all problematic for
routine use.

I will point out that currently IDEA 9.0.3 EAP #95.311 has one problem
that I encounter: You must manually log into any Subversion servers
your projects use once for each launch of IDEA.

Randall Schulz

I tried the EAP about 2 weeks ago - specifically prompted by this issue.
It crashed roughly every 10 minutes without indicating why, when I was working on unrelated Java code with a very critical deadline. After reading on the JetBrains site that they don't even consider EAPs to be up to the standard of betas, I've lostany confidence in the idea of using an EAP release.
I've had the IDE offer me two updates to the IntelliJ/Scala plugin since this bug was allegedly fixed, so I'd expect to see it working under my installation now.


On 10 July 2010 02:07, Randall R Schulz <rschulz@sonic.net> wrote:

On Friday July 9 2010, Kevin Wright wrote:
> looks like this issue:
>
> http://youtrack.jetbrains.net/issue/SCL-2048?query=ScalaTest09Scala28
>Runner is still present in the latest build of the IDEA/Scala plugin
> for 9.0.2
>
> It's been present from at least 2..0.RC3 through to the present
> 2.8.0.RC7
>
> Maia is not an option for me, I use the IDE heavily for my day job
> (including some small pieces of Scala) and it absolutely must be
> stable. If I update to the latest scala plugin when running under
> Maia then it stops working under 9.0.2

Maia _is_ IDEA 9.

JetBrains EAPs for IDEA are entirely stable enough for
everyday "real-world" or "professional" use. Only early in the
development of a new major release is this not generally true. It is
rare for the EAP of a point release to be at all problematic for
routine use.

I will point out that currently IDEA 9.0.3 EAP #95.311 has one problem
that I encounter: You must manually log into any Subversion servers
your projects use once for each launch of IDEA.


Randall Schulz

--
Kevin Wright

mail/google talk: kev.lee.wright@gmail.com
wave: kev.lee.wright@googlewave.com
skype: kev.lee.wright
twitter: @thecoda

On Saturday July 10 2010, Kevin Wright wrote:
> I tried the EAP about 2 weeks ago - specifically prompted by this
> issue.
>
> It crashed roughly every 10 minutes without indicating why, when
> I was working on unrelated Java code with a very critical deadline.
> After reading on the JetBrains site that they don't even consider
> EAPs to be up to the standard of betas, I've lost any confidence in
> the idea of using an EAP release.

It sounds like the "Card Marking Optimization Issue" in the Sun JVM
1.6.0_u18, since fixed and for which a work-around exists (see [1] for
details).

> I've had the IDE offer me two updates to the IntelliJ/Scala plugin
> since this bug was allegedly fixed, so I'd expect to see it working
> under my installation now.

Which bug? Do you know anything about this bug other than that "it
crashed?"

This is a fast-moving area (Scala for IDEA) and you need to run the
nightlies to keep up with bug fixes and new feature implementation.

[1]

Randall Schulz

Card marking was the obvious risk and the first thing I checked.  It had all the right symptoms of the IDE just terminating abruptly with no fanfare. I'm also not getting any problems with the (appropriately named) stable release.
In general though, I try and avoid the bad scientist's approach of changing everything at once.  So I'll work with the latest known-good stable release of both the JDK and IDE whilst using the Scala libraries and plugin at the bleeding edge - that way I can control at least some of my variables...

Out of curiosity, does anyone know of a good reason why the Scala plugin has to target such potentially unstable builds of the IDE?  My understanding is that 9.0.3 should primarily be a bugfix release without any additional functionality that a plugin might need.


On 10 July 2010 15:24, Randall R Schulz <rschulz@sonic.net> wrote:

On Saturday July 10 2010, Kevin Wright wrote:
> I tried the EAP about 2 weeks ago - specifically prompted by this
> issue.
>
> It crashed roughly every 10 minutes without indicating why, when
> I was working on unrelated Java code with a very critical deadline.
> After reading on the JetBrains site that they don't even consider
> EAPs to be up to the standard of betas, I've lost any confidence in
> the idea of using an EAP release.

It sounds like the "Card Marking Optimization Issue" in the Sun JVM
1.6.0_u18, since fixed and for which a work-around exists (see [1] for
details).


> I've had the IDE offer me two updates to the IntelliJ/Scala plugin
> since this bug was allegedly fixed, so I'd expect to see it working
> under my installation now.

Which bug? Do you know anything about this bug other than that "it
crashed?"

This is a fast-moving area (Scala for IDEA) and you need to run the
nightlies to keep up with bug fixes and new feature implementation.


[1] <http://java.sun.com/javase/6/webnotes/6u18.html>


Randall Schulz

--
Kevin Wright

mail/google talk: kev.lee.wright@gmail.com
wave: kev.lee.wright@googlewave.com
skype: kev.lee.wright
twitter: @thecoda