Nabble - Scala - Tools

[scala-tools] [netbeans] Ctrl-O regression

2009-11-12T10:51:57Z

Caoyuan,

It seems like after last commits Ctrl-O stopped working.

Andrew

Re: [scala-tools] [eclipse] Java problems in scala files

2009-11-12T09:14:03Z

2009/11/11 Miles Sabin <miles@...>:
> OK, that shows Scala sources being treated as Java. That indicates
> that the Scala plugins haven't started correctly for some reason or
> other. You say you've verified that JDT Weaving is enabled, and
> presumably you've followed the heap configuration and troubleshooting
> instructions here,
>
> http://www.scala-lang.org/node/94

Yup, though the most heap I could get was 800MB but it should be enough.

>
> If so then I'd suggest starting from a fresh Eclipse install and
> workspace and seeing if we can at least create a basic "Hello world"
> Scala project. If that's successful we can try and see what differs
> from the install/workspace that's causing the problem.

Weird, first I've tried in fresh workspace but it failed, then I unpacked
whole new fresh eclipse and it worked.
After that, I started doing some semi-random changes in my old eclipse
like changing workspaces, restarting with -clean, reinstalling scala and
finally I think after disabling and re-enabling weaving something worked:
a file icon changed from [J] to [S] but opening it produced error like "Unable
to open editor ID scala something". On second attempt (reopening project)
it opened without syntax coloring. One more restart fixed that and cleaning
project removed remaining syntax errors that were reported.
Everything seems to work now.

Re: [scala-tools] VisualVM and Scala

2009-11-11T15:26:51Z

On 11/11/2009, at 8:35 PM, Iulian Dragos wrote:

On Wed, Nov 11, 2009 at 5:38 AM, Tony Sloane <inkytonik@...> wrote:

Profiler Agent Error: with message: Redefinition failed with error 69
Check JVMTI documentation for this error code.

The JVMTI documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html#ErrorSection)
says that this error means

JVMTI_ERROR_NAMES_DONT_MATCH (69)
The class name defined in the new class file is different from the name in the old class object.

Probably Scala bytecode does not follow some Java naming convention, but otherwise the error message is quite useless. Have you noticed some pattern on those class names? Are they anonymous functions or top-level objects?

They appear to be anonymous functions. At least the list printed out seems to include only those. Yet, when I pick one, then look at the original class file and the one written by the profiler agent, they seem to be the same, or at least use the same names. I've run out of time to pursue this at the moment, but later on I may be able to get back to it and see if I can get further.

Each occurrence of this error (and there are many) pops up a dialog box that has to be dismissed manually. Even if the error can be ignored without affecting the profiling results, it's not practical to dismiss it this way, so I'd like to remove the error if possible.

I would file a bug report on VisualVM, it seems like this is not an error the user should be bothered with, especially since things go well from there on.

Well, it's not entirely clear that things do go well. Profiling data is produced, but given the errors, who knows exactly which classes are being run.

Any recommendations for Scala profiling tools?

I, and a few others in the Scala team, use YourKit. It's free for open-source projects, and works pretty well.

Thanks, I will take a look at YourKit.

cheers,

Tony

Re: [scala-tools] VisualVM and Scala

2009-11-11T01:35:31Z

On Wed, Nov 11, 2009 at 5:38 AM, Tony Sloane <inkytonik@...> wrote:

Profiler Agent Error: with message: Redefinition failed with error 69
Check JVMTI documentation for this error code.

The JVMTI documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html#ErrorSection)
says that this error means

JVMTI_ERROR_NAMES_DONT_MATCH (69)
The class name defined in the new class file is different from the name in the old class object.

Probably Scala bytecode does not follow some Java naming convention, but otherwise the error message is quite useless. Have you noticed some pattern on those class names? Are they anonymous functions or top-level objects?

Each occurrence of this error (and there are many) pops up a dialog box that has to be dismissed manually. Even if the error can be ignored without affecting the profiling results, it's not practical to dismiss it this way, so I'd like to remove the error if possible.

I would file a bug report on VisualVM, it seems like this is not an error the user should be bothered with, especially since things go well from there on.

Any recommendations for Scala profiling tools?

I, and a few others in the Scala team, use YourKit. It's free for open-source projects, and works pretty well.

iulian

thanks,
Tony

--
« Je déteste la montagne, ça cache le paysage »
Alphonse Allais

[scala-tools] VisualVM and Scala

2009-11-10T20:38:13Z

Has anyone tried VisualVM 1.2.1 (https://visualvm.dev.java.net) with
Scala apps?

I'm using Scala version 2.7.7.final (Java HotSpot(TM) 64-Bit Server
VM, Java 1.6.0_15) on Mac OS X 10.6.1.

When the tool is instrumenting the running Scala program, I get many
errors of the form

Profiler Agent Error: with message: Redefinition failed with error 69
Check JVMTI documentation for this error code.

The JVMTI documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html#ErrorSection
)
says that this error means

JVMTI_ERROR_NAMES_DONT_MATCH (69)
The class name defined in the new class file is different from the
name in the old class object.

Each occurrence of this error (and there are many) pops up a dialog
box that has to be dismissed manually. Even if the error can be
ignored without affecting the profiling results, it's not practical to
dismiss it this way, so I'd like to remove the error if possible.

Is there any hope of using this tool with Scala? Any recommendations
for Scala profiling tools?

thanks,
Tony

Re: [scala-tools] [eclipse] Java problems in scala files

2009-11-10T16:09:24Z

2009/11/11 Miles Sabin <miles@...>:

> 2009/11/10 Marcin Wiśnicki <mwisnicki@...>:
>> Is this bug supposed to be fixed:
>> http://old.nabble.com/-scala-tools--Scala-IDE-errors-to25762989.html
>>
>> I seem to suffer from it on latest plugin (2.7.7) with Eclipse 3.5.1
>> (win32) with JavaEE, C++, Maven and Subversive but no Groovy, which
>> was suspected in that thread.
>>
>> JDT weaving is enabled. There are no errors in the error (workspace) log.
>
> That thread is a bit of a mish mash ... can you tell me what you're
> actually seeing?

Exact same thing as the author of the thread:

http://old.nabble.com/attachment/25762989/0/scala-errors.JPG

[sorry for second message but I forgot to cc list previously]

Re: [scala-tools] [eclipse] Java problems in scala files

2009-11-10T15:57:51Z

2009/11/10 Marcin Wiśnicki <mwisnicki@...>:
> Is this bug supposed to be fixed:
> http://old.nabble.com/-scala-tools--Scala-IDE-errors-to25762989.html
>
> I seem to suffer from it on latest plugin (2.7.7) with Eclipse 3.5.1
> (win32) with JavaEE, C++, Maven and Subversive but no Groovy, which
> was suspected in that thread.
>
> JDT weaving is enabled. There are no errors in the error (workspace) log.

That thread is a bit of a mish mash ... can you tell me what you're
actually seeing?

Cheers,

Miles

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

[scala-tools] [eclipse] Java problems in scala files

2009-11-10T15:41:38Z

Is this bug supposed to be fixed:
http://old.nabble.com/-scala-tools--Scala-IDE-errors-to25762989.html

I seem to suffer from it on latest plugin (2.7.7) with Eclipse 3.5.1
(win32) with JavaEE, C++, Maven and Subversive but no Groovy, which
was suspected in that thread.

JDT weaving is enabled. There are no errors in the error (workspace) log.

Re: [scala-tools] Eclipse fails to load after updating plug-in

2009-11-09T13:39:49Z

this happens a lot for me on os x and eclipse 3.5.x. The workaround is to keep a copy of the original configuration/config.ini and replace the one you get after upgrades. Perhaps it will work for you?

https://bugs.eclipse.org/bugs/show_bug.cgi?id=260644

Re: [scala-tools] Eclipse fails to load after updating plug-in

2009-11-09T08:24:46Z

On 09/11/2009 17:20, Ismael Juma wrote:
> After updating the Scala plugin, Eclipse asks if one wants to restart.
> If this is accepted, Eclipse hangs on restart. Killing it and starting
> again works.

I see that also from time to time, it seems less frequent now - but I
can't guaranty that feeling.

--
Francois Armand

Re: [scala-tools] Eclipse fails to load after updating plug-in

2009-11-09T08:20:34Z

On Mon, 2009-11-09 at 16:03 +0000, Miles Sabin wrote:

> On Mon, Nov 9, 2009 at 3:58 PM, Mohamed Bana <mohamed@...> wrote:
> > I've noticed on more than one occasion that after updating the nightly
> > plug-in Eclipse will fail to load, if it is started normally. It just
> > doesn't progress. That work around is to use
> >
> > $ ./eclipse -clean
> >
> > Is this intended?
>
> It's not intended, but it seem to be a known generic Eclipse bug. If
> you're running of trunk and updating regularly then I would definitely
> recommend using -clean.

After updating the Scala plugin, Eclipse asks if one wants to restart.
If this is accepted, Eclipse hangs on restart. Killing it and starting
again works. Seems like a similar problem and it has been happening for
a while (I remember this complaint from other people in the 2.7.x series
too). It doesn't happen with other plugins that I have tried, so it
seems to me that there may be more to it than just a generic Eclipse
bug.

Best,
Ismael

Re: [scala-tools] Eclipse fails to load after updating plug-in

2009-11-09T08:03:34Z

GTK implies that this is a linux issue.

I've also seen it on Windows, though not recently I have to admit.

On Mon, Nov 9, 2009 at 3:58 PM, Mohamed Bana <mohamed@...> wrote:

> Hi folks,
>
> I've noticed on more than one occasion that after updating the nightly
> plug-in Eclipse will fail to load, if it is started normally. It just
> doesn't progress. That work around is to use
>
> $ ./eclipse -clean
>
> Is this intended?
>
> Here is the log
>
> $ ./eclipse
> Gtk-Message: Failed to load module "canberra-gtk-module":
> /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class:
> ELFCLASS64
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [org.eclipse.equinox.weaving.hook] info adding AspectJ hooks ...
> [org.eclipse.equinox.weaving.hook] info removing supplementer
> ch.epfl.lamp.sdt.aspects
> [org.eclipse.equinox.weaving.hook] info removing supplementer
> org.eclipse.contribution.weaving.jdt
> [org.eclipse.equinox.weaving.hook] info removing supplementer
> ch.epfl.lamp.sdt.aspects
> [org.eclipse.equinox.weaving.hook] info removing supplementer
> ch.epfl.lamp.sdt.aspects
> [org.eclipse.equinox.weaving.hook] info removing supplementer
> org.eclipse.contribution.weaving.jdt
> [org.eclipse.equinox.weaving.hook] info removing supplementer
> ch.epfl.lamp.sdt.aspects
> [org.eclipse.equinox.weaving.hook] info removing supplementer
> org.eclipse.contribution.weaving.jdt
>
>
> —Mohamed
>

Re: [scala-tools] Eclipse fails to load after updating plug-in

2009-11-09T08:03:21Z

On Mon, Nov 9, 2009 at 3:58 PM, Mohamed Bana <mohamed@...> wrote:
> I've noticed on more than one occasion that after updating the nightly
> plug-in Eclipse will fail to load, if it is started normally. It just
> doesn't progress. That work around is to use
>
> $ ./eclipse -clean
>
> Is this intended?

It's not intended, but it seem to be a known generic Eclipse bug. If
you're running of trunk and updating regularly then I would definitely
recommend using -clean.

Cheers,

Miles

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

[scala-tools] Eclipse fails to load after updating plug-in

2009-11-09T07:58:24Z

Hi folks,

I've noticed on more than one occasion that after updating the nightly plug-in Eclipse will fail to load, if it is started normally. It just doesn't progress. That work around is to use

$ ./eclipse -clean

Is this intended?

Here is the log

$ ./eclipse
Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: ELFCLASS64

[org.eclipse.equinox.weaving.hook] info adding AspectJ hooks ...
[org.eclipse.equinox.weaving.hook] info removing supplementer ch.epfl.lamp.sdt.aspects
[org.eclipse.equinox.weaving.hook] info removing supplementer org.eclipse.contribution.weaving.jdt
[org.eclipse.equinox.weaving.hook] info removing supplementer ch.epfl.lamp.sdt.aspects
[org.eclipse.equinox.weaving.hook] info removing supplementer ch.epfl.lamp.sdt.aspects
[org.eclipse.equinox.weaving.hook] info removing supplementer org.eclipse.contribution.weaving.jdt
[org.eclipse.equinox.weaving.hook] info removing supplementer ch.epfl.lamp.sdt.aspects
[org.eclipse.equinox.weaving.hook] info removing supplementer org.eclipse.contribution.weaving.jdt

—Mohamed

Re: [scala-tools] Eclipse plugin with scala-maven-pugin

2009-11-07T02:50:03Z

Ismael Juma a écrit :
> I leave them both, but I make sure the versions match. That is the most
> important bit, as far as I can tell.

OK, so I will continue this way, to.

Thanks for answers !

--
Francois Armand
http://fanf42.blogspot.com

Re: [scala-tools] Eclipse plugin with scala-maven-pugin

2009-11-06T11:45:34Z

> As it does not feel good to have two jars of the same lib in the path, I
> was wondering what is the standard behaviour for that case. Remove the
> Eclipse plugin's scala lib container from the path ?

It's a bit odd to have one Scala lib directly in the project for the SDT
and one other in the Maven dependencies. However, if you use the latest
snapshots of both, they should be compatible.

This is my Maven-plug config and dependency:

<plugin>
<groupId>org.scala-tools</groupId>
<artifactId>maven-scala-plugin</artifactId>
<configuration>
<charset>UTF-8</charset>
<encoding>UTF-8</encoding>
<jvmArgs>
<jvmArg>-Xms64m</jvmArg>
<jvmArg>-Xmx1g</jvmArg>
</jvmArgs>
<sourceDir>src/main/java</sourceDir>
</configuration>
</plugin>

`maven-scala-plugin' deduces the Scala-lib and Scala-compiler version
from the `scala-library' dependency, which looks like this:

<dependency>
<groupId>org.scala-lang</groupId>
<artifactId>scala-library</artifactId>
<version>${scalaVersion}</version>
</dependency>

where `scalaVersion' is a property:

<properties>
...
<scalaVersion>2.8.0-SNAPSHOT</scalaVersion>
...
</properties>

These are the relevant repositories:

<repositories>
<repository>
<id>org.scala-tools.repository.releases</id>
<name>Scala-Tools Releases</name>
<url>http://scala-tools.org/repo-releases</url>
</repository>
<repository>
<id>org.scala-tools.repository.snapshots</id>
<name>Scala-Tools Snapshots</name>
<url>http://scala-tools.org/repo-snapshots</url>
</repository>
</repositories>

This setup works fine for me, both in Eclipse and on the command line
with Maven.

Hope this helps,

---Ph.

Re: [scala-tools] Eclipse plugin with scala-maven-pugin

2009-11-06T11:33:14Z

On Fri, 2009-11-06 at 20:21 +0100, Francois Armand wrote:
> Miles Sabin a écrit :
> > If you do that then don't come crying to me when it breaks Eclipse ...
>
> That is exactly why I ask before doing it, and was wondering what it is
> the normal thing to do : let the two jars in the classpath ? If so, do I
> have to put the plugin container higher than the maven container ?

I leave them both, but I make sure the versions match. That is the most
important bit, as far as I can tell.

Best,
Ismael

Re: [scala-tools] Eclipse plugin with scala-maven-pugin

2009-11-06T11:21:33Z

Miles Sabin a écrit :
> If you do that then don't come crying to me when it breaks Eclipse ...

That is exactly why I ask before doing it, and was wondering what it is
the normal thing to do : let the two jars in the classpath ? If so, do I
have to put the plugin container higher than the maven container ?

--
Francois Armand
http://fanf42.blogspot.com

Re: [scala-tools] Eclipse plugin with scala-maven-pugin

2009-11-06T11:12:31Z

On Fri, Nov 6, 2009 at 7:05 PM, Francois Armand <fanf42@...> wrote:
> As it does not feel good to have two jars of the same lib in the path, I was
> wondering what is the standard behaviour for that case. Remove the Eclipse
> plugin's scala lib container from the path ?

If you do that then don't come crying to me when it breaks Eclipse ...

Cheers,

Miles

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

Re: [scala-tools] Eclipse plugin with scala-maven-pugin

2009-11-06T11:08:00Z

On Fri, Nov 6, 2009 at 2:05 PM, Francois Armand <fanf42@...> wrote:

Hello,

I use the Scala eclipse plugin alongs with maven-scala-plugin. Eclipse plugin brings a classpath container with the Scala library, and I have in the pom a dependency with Scala-lib - what means that I have to Scala-lib in the classpath.

As it does not feel good to have two jars of the same lib in the path, I was wondering what is the standard behaviour for that case. Remove the Eclipse plugin's scala lib container from the path ?

In the 2.7.4 verison of the plugin, I get away with this all the time, so yes that would be the ideal. I'm not sure about other versions, as I haven't tried.

- Josh

[scala-tools] Eclipse plugin with scala-maven-pugin

2009-11-06T11:05:15Z

Hello,

I use the Scala eclipse plugin alongs with maven-scala-plugin. Eclipse
plugin brings a classpath container with the Scala library, and I have
in the pom a dependency with Scala-lib - what means that I have to
Scala-lib in the classpath.

As it does not feel good to have two jars of the same lib in the path, I
was wondering what is the standard behaviour for that case. Remove the
Eclipse plugin's scala lib container from the path ?

Thanks !

--
Francois Armand
http://fanf42.blogspot.com

Re: [scala-tools] 2.8 REPL on Mac OS X (Snow Leopard, Java 1.6.0_15) broken?

2009-11-03T00:38:19Z

Figured it out.

I had problems with jline in the past, and had created a
.jlinebindings.properties file, which screwing up input for scala. It
doesn't look like scala 2.7.7.final used jline.

I apologize for the spam, and thanks to Paul for the help.

Kevin

Re: [scala-tools] 2.8 REPL on Mac OS X (Snow Leopard, Java 1.6.0_15) broken?

2009-11-02T23:35:35Z

On Mon, Nov 2, 2009 at 10:35 PM, Paul Phillips <paulp@...> wrote:
> On Mon, Nov 02, 2009 at 10:07:12PM -0800, Kevin Squire wrote:
>> That is why I was checking here. If you have it working on Snow
>> Leopard, can you give me some hints on your setup? Did you do
>> anything special? I'm rather frustrated.
>
> I did nothing special. What does scala -verbose output? Where does it
> look stuck if you send it SIGQUIT?

I didn't know about scala -verbose. Thanks for telling me about that,
though it doesn't tell me much. SIGQUIT doesn't really tell much
either. In both cases, it seems to be running, just not receiving any
input--it doesn't even look stuck. Output similar to 2.7.7.final
(which works). My terminal is the same for each version of scala, and
I've stripped all crud out of my environment.

Would you be willing to look at the output and compare it to the
output on your system, or tell me if you see something?

Kevin

Re: [scala-tools] 2.8 REPL on Mac OS X (Snow Leopard, Java 1.6.0_15) broken?

2009-11-02T19:14:19Z

On Mon, Nov 02, 2009 at 06:25:40PM -0800, Kevin Squire wrote:
> The REPL for recent 2.8 nightly builds is broken (for me) on Mac OS X
> (Snow Leopard, Java 1.6.0_15). The ones I've checked are r19316 (28
> Oct) and r19352 (30 Oct). Compiling and running programs works fine.
> When the REPL is run, however, it brings up the prompt, but then hangs
> on any input. Backspace is also broken.
>
> Is this known, or should I file a ticket?

Emphasis on "for you", so please don't file a ticket unless you can
describe something reproducible.

--
Paul Phillips | These are the climbs that apply men's soles.
Caged Spirit |
Empiricist |
i pull his palp! |----------* http://www.improving.org/paulp/ *----------

[scala-tools] 2.8 REPL on Mac OS X (Snow Leopard, Java 1.6.0_15) broken?

2009-11-02T18:25:40Z

Hello,

Just wanted to check here before filing a ticket. A search here and
in TRAC didn't find anything.

The REPL for recent 2.8 nightly builds is broken (for me) on Mac OS X
(Snow Leopard, Java 1.6.0_15). The ones I've checked are r19316 (28
Oct) and r19352 (30 Oct). Compiling and running programs works fine.
When the REPL is run, however, it brings up the prompt, but then hangs
on any input. Backspace is also broken.

Is this known, or should I file a ticket?

Kevin

Re: [scala-tools] Problems with ScalaTest (Scala 2.8)

2009-11-01T13:05:51Z

> Add the scala-tools.org repository. It has all the recent nightlies:
>
> http://scala-tools.org/repo-snapshots/org/scala-lang/scala-compiler/2.8.0-SNAPSHOT/

Awesome! I had this as a plug-in repo already but not for Scala itself.
Now Maven uses a decent, recent compiler and lib on the console as well!
That fulfills a great desire---thanks a lot, Ismael!

---Ph.

Re: [scala-tools] Problems with ScalaTest (Scala 2.8)

2009-11-01T12:34:26Z

On Sun, 2009-11-01 at 21:23 +0100, Philip Köster wrote:
> > There's actually a new version of scalatest against a
> > post-rename-of-VectorLike nightly of Scala. I successfully used it
> > yesterday.
> > The version is 1.0-for-scala-2.8.0.20091026-SNAPSHOT . No guarantees though.
>
> This one works fine for me in Eclipse. On the console with Maven, tough,
> I get a `java.lang.NoClassDefFoundError: scala/collection/Seq'. The
> Maven plug uses Scala 2.8.0.r18462-b20090811081019 (when will there be a
> newer one on Central?).

Add the scala-tools.org repository. It has all the recent nightlies:

http://scala-tools.org/repo-snapshots/org/scala-lang/scala-compiler/2.8.0-SNAPSHOT/

Ismael

Re: [scala-tools] Problems with ScalaTest (Scala 2.8)

2009-11-01T12:23:35Z

> There's actually a new version of scalatest against a
> post-rename-of-VectorLike nightly of Scala. I successfully used it
> yesterday.
> The version is 1.0-for-scala-2.8.0.20091026-SNAPSHOT . No guarantees though.

This one works fine for me in Eclipse. On the console with Maven, tough,
I get a `java.lang.NoClassDefFoundError: scala/collection/Seq'. The
Maven plug uses Scala 2.8.0.r18462-b20090811081019 (when will there be a
newer one on Central?).

Now it looks like 2.8 isn't 2.8 isn't 2.8. :)

Regards
---Ph.

Re: [scala-tools] Problems with ScalaTest (Scala 2.8)

2009-11-01T11:33:11Z

On Sun, Nov 1, 2009 at 12:29 PM, Ismael Juma <mlists@...> wrote:
> On Sun, 2009-11-01 at 20:08 +0100, Philip Köster wrote:
>> I looked around in my Scala library, and indeed there is no
>> `scala.collection.VectorLike', not even in any other package.
>>
>> So what gives?
>
> You need to compile ScalaTest with trunk. The snapshot used to compile
> the binary you used is too old for the library used by the Eclipse
> plugin for Scala.

There's actually a new version of scalatest against a
post-rename-of-VectorLike nightly of Scala. I successfully used it
yesterday.
The version is 1.0-for-scala-2.8.0.20091026-SNAPSHOT . No guarantees though.

-- David

>
> Best,
> Ismael
>
>

Re: [scala-tools] Problems with ScalaTest (Scala 2.8)

2009-11-01T11:29:28Z

On Sun, 2009-11-01 at 20:08 +0100, Philip Köster wrote:
> I looked around in my Scala library, and indeed there is no
> `scala.collection.VectorLike', not even in any other package.
>
> So what gives?

You need to compile ScalaTest with trunk. The snapshot used to compile
the binary you used is too old for the library used by the Eclipse
plugin for Scala.

Best,
Ismael

[scala-tools] Problems with ScalaTest (Scala 2.8)

2009-11-01T11:08:53Z

Now that I finished reading ``Programming in Scala," I wanted to go
ahead and have a good look at ScalaTest. I'm using Eclipse with the
latest nightly of the Scala IDE, which uses Scala library 2.8.0.r19360.
The version of the ScalaTest Maven artifact is 1.0-for-scala-2.8.0-SNAPSHOT.

This is my test class, and it compiles fine:

class MyTest extends AssertionsForJUnit {
@Test
def testEqEqEq() {
val buf = new StringBuilder("ScalaTest is ")
buf.append("fun!")
assert(buf.toString === "ScalaTest is funx!")
}
}

Naturally, the `===' comparison fails here, and when it does so I get this:

java.lang.NoClassDefFoundError: scala/collection/VectorLike
at org.scalatest.Assertions$Equalizer.$eq$eq$eq(Assertions.scala:247)
. . .

I looked around in my Scala library, and indeed there is no
`scala.collection.VectorLike', not even in any other package.

So what gives?

---Ph.

Re: [scala-tools] IDEA Scala plugin

2009-10-30T18:16:34Z

If the plugin version you have now is grayed in IDEA I'd recommend you to check its version (Help -> About in IntelliJ menu). There you may see the build number. The last stable one is 90.122 and the right column on the nightly builds' page contains this information about a compatible IDEA version.

Cheers!

Ilya

2009/10/31 Silvio Bierman <sbierman@...>

Ilya Sergey (JetBrains) wrote:
>
> Hi.
>
> I just want to remind, that excep plugin repository, actual Scala plugin
> versions may be downloaded from
> http://www.jetbrains.net/confluence/display/SCA/Scala+Plugin+Nightly+Builds
> where you may compare your IDEA version with the one supported by the last
> plugin build.
>

That is where I got the plugin build but I do not see any information on
which IDEA version is supported is supported by which build.

Ilya Sergey (JetBrains) wrote:
>
> An here
> http://www.jetbrains.net/confluence/display/SCA/How+to+build+Scala+plugin+for+IntelliJ+IDEA+from+scratch
> we have some advices on how to build plugin and install it which is also
> applicable for nightly builds.
>

Yes, I found that page earlier. But I skipped the building part since I can
download builds from the previous page and the build process there is not
very practical for a Windows user. I do not know what git is and I do not
have an Ant version hat I can run from the command line, only Ants embedded
in IDEA and Eclipse.

But the part about unzipping in the plugin folder that is mentioned there is
what is failing here. IDEA sees the plugin but lists it as an incompatible
version.

Is IDEA CE not the latest IDEA version and is that why the plugin does not
match? I knew that CE is lacking some functionality (which I don't need) but
was under the impression that it is a recent version.

Gr. Silvio

--
View this message in context: http://old.nabble.com/-scala-tools--IDEA-Scala-plugin-tp26086506p26138932.html

Sent from the Scala - Tools mailing list archive at Nabble.com.

!DSPAM:52,4aeb8e60318475786344116!

Re: [scala-tools] IDEA Scala plugin

2009-10-30T18:09:42Z

Ilya Sergey (JetBrains) wrote:

Hi.

I just want to remind, that excep plugin repository, actual Scala plugin
versions may be downloaded from
http://www.jetbrains.net/confluence/display/SCA/Scala+Plugin+Nightly+Builds
where you may compare your IDEA version with the one supported by the last
plugin build.

That is where I got the plugin build but I do not see any information on which IDEA version is supported is supported by which build.

Ilya Sergey (JetBrains) wrote:

An here
http://www.jetbrains.net/confluence/display/SCA/How+to+build+Scala+plugin+for+IntelliJ+IDEA+from+scratch
we have some advices on how to build plugin and install it which is also
applicable for nightly builds.

Yes, I found that page earlier. But I skipped the building part since I can download builds from the previous page and the build process there is not very practical for a Windows user. I do not know what git is and I do not have an Ant version hat I can run from the command line, only Ants embedded in IDEA and Eclipse.

But the part about unzipping in the plugin folder that is mentioned there is what is failing here. IDEA sees the plugin but lists it as an incompatible version.

Is IDEA CE not the latest IDEA version and is that why the plugin does not match? I knew that CE is lacking some functionality (which I don't need) but was under the impression that it is a recent version.

Gr. Silvio

Re: [scala-tools] IDEA Scala plugin

2009-10-30T17:32:19Z

Hi.

I just want to remind, that excep plugin repository, actual Scala plugin versions may be downloaded from
http://www.jetbrains.net/confluence/display/SCA/Scala+Plugin+Nightly+Builds
where you may compare your IDEA version with the one supported by the last plugin build.
An here
http://www.jetbrains.net/confluence/display/SCA/How+to+build+Scala+plugin+for+IntelliJ+IDEA+from+scratch
we have some advices on how to build plugin and install it which is also applicable for nightly builds.

Cheers!
Ilya

2009/10/30 Silvio Bierman <sbierman@...>

Well, not exactly. It worked for the same version of the plugin but the
current build remains disabled and is listed in red meaning that it is
incompatible with the current version of IDEA.

Gr. Silvio

--
View this message in context: http://old.nabble.com/-scala-tools--IDEA-Scala-plugin-tp26086506p26129535.html

Sent from the Scala - Tools mailing list archive at Nabble.com.

!DSPAM:52,4aeae0f7182722090119686!

Re: [scala-tools] Multiple classes displayed in IntelliJ

2009-10-30T14:55:49Z

On Friday October 30 2009, Randy Kahle wrote:

> I've checked that several times as that was my initial conclusion
> also.
>
> I've discovered a new bit of information as I was working on the
> files. If I have a compiler error then the 2nd displayed instance
> goes away. Once I fix the error and compile, they both show up again.
> I'm thinking it is showing a source version of a compiled instance?
> That sounds weird, but maybe.
>
> I have a non-standard configuration because I'm compiling for
> NetKernel and it prefers that I have source and compiled class files
> in the same tree location. Maybe it's related to that.

I think that's likely. I've never known anyone to actually prefer to
have .class files cluttering their source directories...

> I'll continue to puzzle on this one.
>
> Thanks! -- Randy

Randall Schulz