Re: Re: Running unit tests?

I'm using the plugin under 3.5 M7 without any serious problems.  There are of course the random error annotations, the occasional confusion with Cmd+D, and an exception here and there.  All things considered though, it's quite usable.

Daniel

On Wed, May 6, 2009 at 4:55 PM, Miles Sabin <miles@milessabin.com> wrote:

On Wed, May 6, 2009 at 10:49 PM, Barry Kaplan <groups1@memelet.com> wrote:
> Miles what eclipse are you running? I'm using M6 against the plugin nightly.
> I definitely do not get the context menu item.

3.4.2.

Strictly speaking unreleased 3.5 Milestone builds aren't supported,
although I would be grateful for bug reports covering issues with
Scala IDE releases or trunk and 3.5 (tho' please try and report
against the most recent Milestone if that's the case ... 3.5M7
currently).

3.5 will be the recommended release for 2.8.0.

Cheers,


Miles

--
Miles Sabin
tel: +44 (0)7813 944 528
skype:  milessabin
http://twitter.com/milessabin

Daniel, are you using 2.7.4-final or the nightly builds? I am using nightly.

On Wed, May 6, 2009 at 11:54 PM, Barry Kaplan wrote:
> Daniel, are you using 2.7.4-final or the nightly builds? I am using nightly.

Oh. I was under the impression that you were using 2.7.4.final ...

Unless you really have a pressing need for the trunk of the Scala
compiler and libraries then I would *very* strongly recommend that you
stick to 2.7.4.final.

Cheers,

Miles

No pressing need. I wanted to test some of the changes in 2.8 (like the
ability to override val's in traits), but it can wait.

What about using eclipse 3.5. I really want the capabilities of the equinox
aspects. Is that fully supported in 3.4?

On Thu, May 7, 2009 at 12:51 AM, Barry Kaplan wrote:
> What about using eclipse 3.5. I really want the capabilities of the equinox
> aspects. Is that fully supported in 3.4?

Absolutely ... that's what the 2.7.4.final release was all about ...

Eclipse 3.4.2 is recommended, 3.5M7 is probably fine (and better in
some ways, esp. for read-only Eclipse installs) but I can't promise
that you won't see occasional quirks ...

Cheers,

Miles

Ok, I just downloaded a fresh 3.4SR2 and installed 2.7.4-final. I create a
new workspace from scratch. I cleared out the target directories and the
.manager directory. I have that simple unit test from above. The run-as
context menu shows only "Scala Application". When I manually create a Junit
run config it says it cannot find any tests.

I created the same test but as a java class in the same package in the
directly as the scala test. /That/ gives me the run as junit menu item, so
at least I know that nothings deeply wrong my eclipse environment.

Sigh. I know that this can be done, but I guess just not for me. I don't
what else I can do that is any simpler just to be able to run a single unit
test. At least before with 3.5 and nightly I was able to to run the simple
junit4 test, if not the ScalaTest tests. Now I can't even do that.

On Thu, May 7, 2009 at 1:35 AM, Barry Kaplan wrote:
> Ok, I just downloaded a fresh 3.4SR2 and installed 2.7.4-final. I create a
> new workspace from scratch. I cleared out the target directories and the
> .manager directory. I have that simple unit test from above. The run-as
> context menu shows only "Scala Application". When I manually create a Junit
> run config it says it cannot find any tests.
>
> I created the same test but as a java class in the same package in the
> directly as the scala test. /That/ gives me the run as junit menu item, so
> at least I know that nothings deeply wrong my eclipse environment.

Send me that project and I'll take a look at it ...

Cheers,

Miles