Can't install netbeans plugin

[Alan]

Hi,

I'm running:

Product Version: NetBeans IDE 6.5.1 (Build 200903060201)
Java: 1.6.0_13; Java HotSpot(TM) Client VM 11.3-b02
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)

And I'm trying to follow the directions here:

http://wiki.netbeans.org/Scala#section-Scala-1.GetStartedWithNetBeans6.5

To install the netbeans plugin: "nb-scala-6.7v1.zip".

I unzip the file and tell Netbeans to install all the *.nbm files, but
I get this:

"Some plugins require plugin org.netbeans.modules.csl.api to be
installed.
The plugin org.netbeans.modules.csl.api is requested in version 1.9.
The following plugin is affected:       Scala Project
Some plugins require plugin External Execution Support to be
installed.
The plugin External Execution Support is requested in version >= 1.13
but only 1.9.1 was found. The following plugin is affected:
      Scala Console
Some plugins require plugin org.netbeans.modules.parsing.api to be
installed.
The plugin org.netbeans.modules.parsing.api is requested in version
1.12. The following plugin is affected:       Scala Project
Some plugins require plugin File System API to be installed.
The plugin File System API is requested in version >= 7.19 but only
7.13.1.1.1 was found. The following plugin is affected:       Scala
Project Some plugins not installed to avoid potential installation
problems."

I have looked around for information on the plugins mentioned, but
have not found anything useful. Perhaps the instructions should be
updated? Or have I missed something?

Thanks,
Alan

[Caoyuan]

Hi,

Please download the newest plugin version 1 for NetBeans 6.7, and use
NetBeans 6.7RC3 or above.

[Alan]

Oh ok, thanks, I got it installed now. But actually I've run into one
more problem. I don't know if I'm just being stupid but when I try to
build a class I get a compiler error:

Could not connect to compilation daemon.
java.lang.Exception: fsc failure
at scala.tools.nsc.CompileSocket.fatal(CompileSocket.scala:53)
at scala.tools.nsc.CompileSocket.getPort(CompileSocket.scala:
175)
etc...

Then:

...\NetBeansProjects\pairwise4\nbproject\build-impl.xml:229: Compile
failed because of an internal compiler error (fsc failure); see the
error output for details.

I can compile and run scala fine from the command line. Any idea
what's wrong?

Thanks,
Alan

[Caoyuan]

Check if you've got SCALA_HOME set

[Alan]

Yes, it is set and I can use it from the command line. Is there maybe
something within Netbeans that needs to be configured? I didn't see
anything to that effect on the wiki.

Thanks,
Alan

[Caoyuan]

Then, check if "scala" is under the environment $PATH ?

[Alan]

Hm, I think I managed to fix it, but I have no idea why it worked.

Since the error says it couldn't connect to the compilation daemon,
and since this daemon is started by fsc, I tried using fsc at the
command line. Now the class is compiling and running in Netbeans just
fine. So I guess maybe for some reason Netbeans is not invoking fcs
properly, or something like that?

Alan

[Caoyuan]

On Thu, Jun 25, 2009 at 9:55 AM, Alan<eah...@gmail.com> wrote:
>
> Hm, I think I managed to fix it, but I have no idea why it worked.
>
> Since the error says it couldn't connect to the compilation daemon,
> and since this daemon is started by fsc, I tried using fsc at the
> command line. Now the class is compiling and running in Netbeans just
> fine. So I guess maybe for some reason Netbeans is not invoking fcs
> properly, or something like that?

I only tested on my MacBook, I does not need to invoke "fsc", just
open NetBeans and the scala project, and click on build everything
works.

But I truly got a feedback that he had to run "scala" or "fsc" first
on his Windows XP, the everything worked.

[helmut]

Hi

I had the same problem: Could not connect to compilation daemon. .....

I run fsc.bat and tell the Antivir "do not block..." -> then it works

Helmut

[helmut]

Op's

Nonsens - run fsc is the right thing

Helmut

[Caoyuan]

On Thu, Jul 2, 2009 at 12:57 AM, helmut<helmut.p...@chello.at> wrote:
>
> Op's
>
> Nonsens - run fsc is the right thing

Thanks for the feedback, I've updated wiki page and blog post about this issue.

--Caoyuan

[Det]

> Thanks for the feedback, I've updated wiki page and blog post about this issue.

Caoyuan, perhaps some background info to this point in wiki
would be nice.

I had the same effect, and it seems to be related to the firewall
First I was noticed about a blocked call and asked for confirmation.
To release the block resulted in the error message of the daemon
either. On a second try I was asked for confirmation again, and
from this time on everything works fine.

KR
Det