Is NetBeans scala plugin dead?

On Fri, Mar 19, 2010 at 7:27 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

It's been a while since the last update of the plugin (as far as I am aware of), so maybe someone here could tell me about it. Should I forget about NetBeans and Scala and go find another IDE?

My experience with the NetBeans plugin is that it's very stable... it just works.  No need for updates IMHO.
 

Thanks

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

I'm actually using the 2.8 version, and it certainly needs update. Lots of crash downs (yes in NetBeans o.O). Many lacks in Java-Scala integration, and better content assistance (like Constructor assistance which I really miss from Java), and it becomes really slow with big Scala files. Anyway, this are just natural evolution of the plugin not a critique :) .

Cheers.

On Fri, Mar 19, 2010 at 2:03 PM, David Pollak <feeder.of.the.bears@gmail.com> wrote:

On Fri, Mar 19, 2010 at 7:27 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

It's been a while since the last update of the plugin (as far as I am aware of), so maybe someone here could tell me about it. Should I forget about NetBeans and Scala and go find another IDE?

My experience with the NetBeans plugin is that it's very stable... it just works.  No need for updates IMHO.
 

Thanks

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

On Fri, Mar 19, 2010 at 10:10 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

I'm actually using the 2.8 version, and it certainly needs update. Lots of crash downs (yes in NetBeans o.O).

Hmmm... I've been using the 2.8.0-Beta1 plugin on NetBeans 6.8 and have not had a single crash.  But crashes are usually due to JVM issues.  If they are JVM issues, then it's not likely that the plugin author can work around them.  Also, I suggest at least 1GB of heap for doing Scala work.
 

Many lacks in Java-Scala integration, and better content assistance (like Constructor assistance which I really miss from Java), and it becomes really slow with big Scala files.

First, increase your heap size.  Second, how big are the files that are causing problems?  Third, how does the performance compare with other Scala IDE plugins?  My experience is that NetBeans is faster than IntelliJ for 1,000+ line files.
 

Anyway, this are just natural evolution of the plugin not a critique :) .

Cheers.

On Fri, Mar 19, 2010 at 2:03 PM, David Pollak <feeder.of.the.bears@gmail.com> wrote:

On Fri, Mar 19, 2010 at 7:27 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

It's been a while since the last update of the plugin (as far as I am aware of), so maybe someone here could tell me about it. Should I forget about NetBeans and Scala and go find another IDE?

My experience with the NetBeans plugin is that it's very stable... it just works.  No need for updates IMHO.
 

Thanks

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

On Fri, Mar 19, 2010 at 10:54 AM, David Pollak
wrote:
>
>
> On Fri, Mar 19, 2010 at 10:10 AM, Rodrigo Cano wrote:
>>
>> I'm actually using the 2.8 version, and it certainly needs update. Lots of
>> crash downs (yes in NetBeans o.O).
>
> Hmmm... I've been using the 2.8.0-Beta1 plugin on NetBeans 6.8 and have not
> had a single crash.  But crashes are usually due to JVM issues.  If they are
> JVM issues, then it's not likely that the plugin author can work around
> them.  Also, I suggest at least 1GB of heap for doing Scala work.

I've had crashes under OS X, but it's reporting a segfault, so I'm
going to blame Apple or Sun.

I've always been working with it with 1GB of heap for the NetBeans, (specifically setted in the conf file). No idea about the others IDE time for handling 1000+ sized files, but I am not willing to leave NetBeans as I really like it and has been using it for years now. I have one concrete file (only 430 lines), that I simply have to edit it from Kate (KDE's text editor) because the NetBeans  (or the plugin should I say) takes about 1 minute to parse it, and every time a make a change (like write) it takes another minute to finish parsing it again. I have no idea why it behaves like this, it doesn't happen to me with any other file, maybe the syntax is to complex(?), it does a lot of traversing trees so a lot a functions are passed, though I would think that that is a complex code.

But I have other kind of weird behaviours, for example it has problems with some classes (don't understand why yet), but it appears to forget about them, so I have to go open the class so that he remembers it back. And if I do a scala parser reset, I have to go back to open it. The classes compile perfectly and are left compiled after that so no idea why it "forgets" about them. When I say forget I mean that they are marked as non existent in every use.

And the last thing. Scala classes are visible to Java code ONLY in the same project (well I think, as this might not happen if you don't use maven as I do), if I use a scala class that was written in other project, the editor thinks the class doesn't exist. This doesn't happen from scala to scala, I mean, my scala classes in others projects "sees" perfectly the classes from my other projects. All this happens in the editor level, compiling always works.

This have been my experience so far.

Cheers.

On Fri, Mar 19, 2010 at 2:54 PM, David Pollak <feeder.of.the.bears@gmail.com> wrote:

On Fri, Mar 19, 2010 at 10:10 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

I'm actually using the 2.8 version, and it certainly needs update. Lots of crash downs (yes in NetBeans o.O).

Hmmm... I've been using the 2.8.0-Beta1 plugin on NetBeans 6.8 and have not had a single crash.  But crashes are usually due to JVM issues.  If they are JVM issues, then it's not likely that the plugin author can work around them.  Also, I suggest at least 1GB of heap for doing Scala work.
 

Many lacks in Java-Scala integration, and better content assistance (like Constructor assistance which I really miss from Java), and it becomes really slow with big Scala files.

First, increase your heap size.  Second, how big are the files that are causing problems?  Third, how does the performance compare with other Scala IDE plugins?  My experience is that NetBeans is faster than IntelliJ for 1,000+ line files.
 

Anyway, this are just natural evolution of the plugin not a critique :) .

Cheers.

On Fri, Mar 19, 2010 at 2:03 PM, David Pollak <feeder.of.the.bears@gmail.com> wrote:

On Fri, Mar 19, 2010 at 7:27 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

It's been a while since the last update of the plugin (as far as I am aware of), so maybe someone here could tell me about it. Should I forget about NetBeans and Scala and go find another IDE?

My experience with the NetBeans plugin is that it's very stable... it just works.  No need for updates IMHO.
 

Thanks

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

I correct a typo: it does a lot of tree traversing so a lot a functions are passed, though I wouldn't think that that is a complex code.



On Fri, Mar 19, 2010 at 3:13 PM, Rodrigo Cano <ioniviil@gmail.com> wrote:

I've always been working with it with 1GB of heap for the NetBeans, (specifically setted in the conf file). No idea about the others IDE time for handling 1000+ sized files, but I am not willing to leave NetBeans as I really like it and has been using it for years now. I have one concrete file (only 430 lines), that I simply have to edit it from Kate (KDE's text editor) because the NetBeans  (or the plugin should I say) takes about 1 minute to parse it, and every time a make a change (like write) it takes another minute to finish parsing it again. I have no idea why it behaves like this, it doesn't happen to me with any other file, maybe the syntax is to complex(?), it does a lot of traversing trees so a lot a functions are passed, though I would think that that is a complex code.

But I have other kind of weird behaviours, for example it has problems with some classes (don't understand why yet), but it appears to forget about them, so I have to go open the class so that he remembers it back. And if I do a scala parser reset, I have to go back to open it. The classes compile perfectly and are left compiled after that so no idea why it "forgets" about them. When I say forget I mean that they are marked as non existent in every use.

And the last thing. Scala classes are visible to Java code ONLY in the same project (well I think, as this might not happen if you don't use maven as I do), if I use a scala class that was written in other project, the editor thinks the class doesn't exist. This doesn't happen from scala to scala, I mean, my scala classes in others projects "sees" perfectly the classes from my other projects. All this happens in the editor level, compiling always works.

This have been my experience so far.

Cheers.

On Fri, Mar 19, 2010 at 2:54 PM, David Pollak <feeder.of.the.bears@gmail.com> wrote:

On Fri, Mar 19, 2010 at 10:10 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

I'm actually using the 2.8 version, and it certainly needs update. Lots of crash downs (yes in NetBeans o.O).

Hmmm... I've been using the 2.8.0-Beta1 plugin on NetBeans 6.8 and have not had a single crash.  But crashes are usually due to JVM issues.  If they are JVM issues, then it's not likely that the plugin author can work around them.  Also, I suggest at least 1GB of heap for doing Scala work.
 

Many lacks in Java-Scala integration, and better content assistance (like Constructor assistance which I really miss from Java), and it becomes really slow with big Scala files.

First, increase your heap size.  Second, how big are the files that are causing problems?  Third, how does the performance compare with other Scala IDE plugins?  My experience is that NetBeans is faster than IntelliJ for 1,000+ line files.
 

Anyway, this are just natural evolution of the plugin not a critique :) .

Cheers.

On Fri, Mar 19, 2010 at 2:03 PM, David Pollak <feeder.of.the.bears@gmail.com> wrote:

On Fri, Mar 19, 2010 at 7:27 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

It's been a while since the last update of the plugin (as far as I am aware of), so maybe someone here could tell me about it. Should I forget about NetBeans and Scala and go find another IDE?

My experience with the NetBeans plugin is that it's very stable... it just works.  No need for updates IMHO.
 

Thanks

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

Thanks for David share his good experience on NetBeans scala plugin,
and Rodrigo's worse experience too.

The released plugin i.e. nb-scala-6.8v1.1.0rc1.zip as described in
http://wiki.netbeans.org/Scala68v1 works under Scala-2.8.0beta1, but
not under recent Scala-2.8.0 nightly built.

The nightly built of NetBeans and Scala Plugin is catching up with
Scala trunk code, the latest that I tested is 2.8.0.r21087.

Per the most recent Scala nightly built, the sig in class file may
have been changed, so all three IDEs may all be broken, I'll wait for
this change stable to sync the plugin code.

So it's recommended to use Scala 2.8.0 beta with released plugin only.
If you are doing development under maven, just keep $scala-version as:
2.8.0.Beta1
and let maven install it from scala-tools.org

In my experience, I can handle 3000+ lines code in one source file of
Scala's compiler trunk code with this plugin with no slow response.

On Sat, Mar 20, 2010 at 2:51 AM, Rodrigo Cano wrote:
> I correct a typo: it does a lot of tree traversing so a lot a functions are
> passed, though I wouldn't think that that is a complex code.
>
>
>
> On Fri, Mar 19, 2010 at 3:13 PM, Rodrigo Cano wrote:
>>
>> I've always been working with it with 1GB of heap for the NetBeans,
>> (specifically setted in the conf file). No idea about the others IDE time
>> for handling 1000+ sized files, but I am not willing to leave NetBeans as I
>> really like it and has been using it for years now. I have one concrete file
>> (only 430 lines), that I simply have to edit it from Kate (KDE's text
>> editor) because the NetBeans  (or the plugin should I say) takes about 1
>> minute to parse it, and every time a make a change (like write) it takes
>> another minute to finish parsing it again. I have no idea why it behaves
>> like this, it doesn't happen to me with any other file, maybe the syntax is
>> to complex(?), it does a lot of traversing trees so a lot a functions are
>> passed, though I would think that that is a complex code.
>>
>> But I have other kind of weird behaviours, for example it has problems
>> with some classes (don't understand why yet), but it appears to forget about
>> them, so I have to go open the class so that he remembers it back. And if I
>> do a scala parser reset, I have to go back to open it. The classes compile
>> perfectly and are left compiled after that so no idea why it "forgets" about
>> them. When I say forget I mean that they are marked as non existent in every
>> use.
>>
>> And the last thing. Scala classes are visible to Java code ONLY in the
>> same project (well I think, as this might not happen if you don't use maven
>> as I do), if I use a scala class that was written in other project, the
>> editor thinks the class doesn't exist. This doesn't happen from scala to
>> scala, I mean, my scala classes in others projects "sees" perfectly the
>> classes from my other projects. All this happens in the editor level,
>> compiling always works.
>>
>> This have been my experience so far.
>>
>> Cheers.
>>
>> On Fri, Mar 19, 2010 at 2:54 PM, David Pollak
>> wrote:
>>>
>>>
>>> On Fri, Mar 19, 2010 at 10:10 AM, Rodrigo Cano
>>> wrote:
>>>>
>>>> I'm actually using the 2.8 version, and it certainly needs update. Lots
>>>> of crash downs (yes in NetBeans o.O).
>>>
>>> Hmmm... I've been using the 2.8.0-Beta1 plugin on NetBeans 6.8 and have
>>> not had a single crash.  But crashes are usually due to JVM issues.  If they
>>> are JVM issues, then it's not likely that the plugin author can work around
>>> them.  Also, I suggest at least 1GB of heap for doing Scala work.
>>>
>>>>
>>>> Many lacks in Java-Scala integration, and better content assistance
>>>> (like Constructor assistance which I really miss from Java), and it becomes
>>>> really slow with big Scala files.
>>>
>>> First, increase your heap size.  Second, how big are the files that are
>>> causing problems?  Third, how does the performance compare with other Scala
>>> IDE plugins?  My experience is that NetBeans is faster than IntelliJ for
>>> 1,000+ line files.
>>>
>>>>
>>>> Anyway, this are just natural evolution of the plugin not a critique :)
>>>> .
>>>>
>>>> Cheers.
>>>>
>>>> On Fri, Mar 19, 2010 at 2:03 PM, David Pollak
>>>> wrote:
>>>>>
>>>>>
>>>>> On Fri, Mar 19, 2010 at 7:27 AM, Rodrigo Cano
>>>>> wrote:
>>>>>>
>>>>>> It's been a while since the last update of the plugin (as far as I am
>>>>>> aware of), so maybe someone here could tell me about it. Should I forget
>>>>>> about NetBeans and Scala and go find another IDE?
>>>>>
>>>>> My experience with the NetBeans plugin is that it's very stable... it
>>>>> just works.  No need for updates IMHO.
>>>>>
>>>>>>
>>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lift, the simply functional web framework http://liftweb.net
>>>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>>>> Follow me: http://twitter.com/dpp
>>>>> Surf the harmonics
>>>>
>>>
>>>
>>>
>>> --
>>> Lift, the simply functional web framework http://liftweb.net
>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>> Follow me: http://twitter.com/dpp
>>> Surf the harmonics
>>
>
>

A good way to make the Scala compiler work really, really hard (and hence both the Netbeans and Eclipse plugin that rely on it to parse source files) is to use constructs like this:
val myList = "a" :: "b" :: "c" :: "d" ...go on for a while.. :: "ZZZ" :: Nil
My understanding is the type inferencer has to work really hard in order to type code like the above.  Netbeans relies on the compiler to tell it various pieces of information, and will invoke the compiler on incremental changes.  This means any code that makes the compiler work really hard will essentially freeze the IDE.
So if you have any code like what's above, rewrite it as:val myList = List("a", "b", ... "ZZZ")
If you have something more complex...maybe look at refactoring it a bit.

On Fri, Mar 19, 2010 at 2:13 PM, Rodrigo Cano <ioniviil@gmail.com> wrote:

I've always been working with it with 1GB of heap for the NetBeans, (specifically setted in the conf file). No idea about the others IDE time for handling 1000+ sized files, but I am not willing to leave NetBeans as I really like it and has been using it for years now. I have one concrete file (only 430 lines), that I simply have to edit it from Kate (KDE's text editor) because the NetBeans  (or the plugin should I say) takes about 1 minute to parse it, and every time a make a change (like write) it takes another minute to finish parsing it again. I have no idea why it behaves like this, it doesn't happen to me with any other file, maybe the syntax is to complex(?), it does a lot of traversing trees so a lot a functions are passed, though I would think that that is a complex code.

But I have other kind of weird behaviours, for example it has problems with some classes (don't understand why yet), but it appears to forget about them, so I have to go open the class so that he remembers it back. And if I do a scala parser reset, I have to go back to open it. The classes compile perfectly and are left compiled after that so no idea why it "forgets" about them. When I say forget I mean that they are marked as non existent in every use.

And the last thing. Scala classes are visible to Java code ONLY in the same project (well I think, as this might not happen if you don't use maven as I do), if I use a scala class that was written in other project, the editor thinks the class doesn't exist. This doesn't happen from scala to scala, I mean, my scala classes in others projects "sees" perfectly the classes from my other projects. All this happens in the editor level, compiling always works.

This have been my experience so far.

Cheers.

On Fri, Mar 19, 2010 at 2:54 PM, David Pollak <feeder.of.the.bears@gmail.com> wrote:

On Fri, Mar 19, 2010 at 10:10 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

I'm actually using the 2.8 version, and it certainly needs update. Lots of crash downs (yes in NetBeans o.O).

Hmmm... I've been using the 2.8.0-Beta1 plugin on NetBeans 6.8 and have not had a single crash.  But crashes are usually due to JVM issues.  If they are JVM issues, then it's not likely that the plugin author can work around them.  Also, I suggest at least 1GB of heap for doing Scala work.
 

Many lacks in Java-Scala integration, and better content assistance (like Constructor assistance which I really miss from Java), and it becomes really slow with big Scala files.

First, increase your heap size.  Second, how big are the files that are causing problems?  Third, how does the performance compare with other Scala IDE plugins?  My experience is that NetBeans is faster than IntelliJ for 1,000+ line files.
 

Anyway, this are just natural evolution of the plugin not a critique :) .

Cheers.

On Fri, Mar 19, 2010 at 2:03 PM, David Pollak <feeder.of.the.bears@gmail.com> wrote:

On Fri, Mar 19, 2010 at 7:27 AM, Rodrigo Cano <ioniviil@gmail.com> wrote:

It's been a while since the last update of the plugin (as far as I am aware of), so maybe someone here could tell me about it. Should I forget about NetBeans and Scala and go find another IDE?

My experience with the NetBeans plugin is that it's very stable... it just works.  No need for updates IMHO.
 

Thanks

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--
http://erikengbrecht.blogspot.com/

On Sat, Mar 20, 2010 at 10:06 PM, Erik Engbrecht
wrote:
> A good way to make the Scala compiler work really, really hard (and hence
> both the Netbeans and Eclipse plugin that rely on it to parse source files)
> is to use constructs like this:
> val myList = "a" :: "b" :: "c" :: "d" ...go on for a while.. :: "ZZZ" :: Nil
> My understanding is the type inferencer has to work really hard in order to
> type code like the above.  Netbeans relies on the compiler to tell it
> various pieces of information, and will invoke the compiler on incremental
> changes.  This means any code that makes the compiler work really hard will
> essentially freeze the IDE.
> So if you have any code like what's above, rewrite it as:
> val myList = List("a", "b", ... "ZZZ")
> If you have something more complex...maybe look at refactoring it a bit.

Exactly right.

>
> On Fri, Mar 19, 2010 at 2:13 PM, Rodrigo Cano wrote:
>>
>> I've always been working with it with 1GB of heap for the NetBeans,
>> (specifically setted in the conf file). No idea about the others IDE time
>> for handling 1000+ sized files, but I am not willing to leave NetBeans as I
>> really like it and has been using it for years now. I have one concrete file
>> (only 430 lines), that I simply have to edit it from Kate (KDE's text
>> editor) because the NetBeans  (or the plugin should I say) takes about 1
>> minute to parse it, and every time a make a change (like write) it takes
>> another minute to finish parsing it again. I have no idea why it behaves
>> like this, it doesn't happen to me with any other file, maybe the syntax is
>> to complex(?), it does a lot of traversing trees so a lot a functions are
>> passed, though I would think that that is a complex code.
>>
>> But I have other kind of weird behaviours, for example it has problems
>> with some classes (don't understand why yet), but it appears to forget about
>> them, so I have to go open the class so that he remembers it back. And if I
>> do a scala parser reset, I have to go back to open it. The classes compile
>> perfectly and are left compiled after that so no idea why it "forgets" about
>> them. When I say forget I mean that they are marked as non existent in every
>> use.
>>
>> And the last thing. Scala classes are visible to Java code ONLY in the
>> same project (well I think, as this might not happen if you don't use maven
>> as I do), if I use a scala class that was written in other project, the
>> editor thinks the class doesn't exist. This doesn't happen from scala to
>> scala, I mean, my scala classes in others projects "sees" perfectly the
>> classes from my other projects. All this happens in the editor level,
>> compiling always works.
>>
>> This have been my experience so far.
>>
>> Cheers.
>>
>> On Fri, Mar 19, 2010 at 2:54 PM, David Pollak
>> wrote:
>>>
>>>
>>> On Fri, Mar 19, 2010 at 10:10 AM, Rodrigo Cano
>>> wrote:
>>>>
>>>> I'm actually using the 2.8 version, and it certainly needs update. Lots
>>>> of crash downs (yes in NetBeans o.O).
>>>
>>> Hmmm... I've been using the 2.8.0-Beta1 plugin on NetBeans 6.8 and have
>>> not had a single crash.  But crashes are usually due to JVM issues.  If they
>>> are JVM issues, then it's not likely that the plugin author can work around
>>> them.  Also, I suggest at least 1GB of heap for doing Scala work.
>>>
>>>>
>>>> Many lacks in Java-Scala integration, and better content assistance
>>>> (like Constructor assistance which I really miss from Java), and it becomes
>>>> really slow with big Scala files.
>>>
>>> First, increase your heap size.  Second, how big are the files that are
>>> causing problems?  Third, how does the performance compare with other Scala
>>> IDE plugins?  My experience is that NetBeans is faster than IntelliJ for
>>> 1,000+ line files.
>>>
>>>>
>>>> Anyway, this are just natural evolution of the plugin not a critique :)
>>>> .
>>>>
>>>> Cheers.
>>>>
>>>> On Fri, Mar 19, 2010 at 2:03 PM, David Pollak
>>>> wrote:
>>>>>
>>>>>
>>>>> On Fri, Mar 19, 2010 at 7:27 AM, Rodrigo Cano
>>>>> wrote:
>>>>>>
>>>>>> It's been a while since the last update of the plugin (as far as I am
>>>>>> aware of), so maybe someone here could tell me about it. Should I forget
>>>>>> about NetBeans and Scala and go find another IDE?
>>>>>
>>>>> My experience with the NetBeans plugin is that it's very stable... it
>>>>> just works.  No need for updates IMHO.
>>>>>
>>>>>>
>>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lift, the simply functional web framework http://liftweb.net
>>>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>>>> Follow me: http://twitter.com/dpp
>>>>> Surf the harmonics
>>>>
>>>
>>>
>>>
>>> --
>>> Lift, the simply functional web framework http://liftweb.net
>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>> Follow me: http://twitter.com/dpp
>>> Surf the harmonics
>>
>
>
>
> --
> http://erikengbrecht.blogspot.com/
>

Hi,

I re-built the plugin trunk code to sync with Scala-2.8.0.r21224, and
will release a new version to catch up with the coming Scala 2.8.0 RC
in next or two weeks.

The NetBeans plugin won't dead, although the latest release was about
4 months ago.

But, it will be living in pulse :-) since I'm also busy on my job work
(a large Scala project).

BTW, for Scala's slower building time comparing to Java, I recommend
to Maven instead of Ant for Scala project, please take a look at:
http://blogtrader.net/blog/how_to_setup_dependencies_aware2

Cheers,
-Caoyuan

On Fri, Mar 19, 2010 at 10:27 PM, Rodrigo Cano wrote:
> It's been a while since the last update of the plugin (as far as I am aware
> of), so maybe someone here could tell me about it. Should I forget about
> NetBeans and Scala and go find another IDE?
>
> Thanks
>

Excellent news. Thanks for the advance :).

On Sat, Mar 20, 2010 at 12:00 PM, Caoyuan <dcaoyuan@gmail.com> wrote:

Hi,

I re-built the plugin trunk code to sync with Scala-2.8.0.r21224, and
will release a new version to catch up with the coming Scala 2.8.0 RC
in next or two weeks.

The NetBeans plugin won't dead, although the latest release was about
4 months ago.

But, it will be living in pulse :-) since I'm also busy on my job work
(a large Scala project).

BTW, for Scala's slower building time comparing to Java, I recommend
to Maven instead of Ant for Scala project, please take a look at:
http://blogtrader.net/blog/how_to_setup_dependencies_aware2

Cheers,
-Caoyuan

On Fri, Mar 19, 2010 at 10:27 PM, Rodrigo Cano <ioniviil@gmail.com> wrote:
> It's been a while since the last update of the plugin (as far as I am aware
> of), so maybe someone here could tell me about it. Should I forget about
> NetBeans and Scala and go find another IDE?
>
> Thanks
>