Hieli-umm road map @release?

[virtualeyes]

I know M2 was delayed, but looking at the road map it appears that worksheet and Juno 4.2 support are the "only" items remaining.

@release date would be a nice to know

Thanks

[virtualeyes]

love the ability to (not) edit in google groups, one and done...

[iulian dragos]

Hi, feature-wise we are pretty close, but we need to polish the things we have. We also aim to release around the time Scala 2.10.0 is out, and their release date is still unclear. We'll follow up soon.

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

[virtualeyes]

Ok, sounds like next year (January or later) then, would be shocked to see Scala 2.10.0 released before then, not even at RC stage yet.

Should we (users of the IDE) be switching to Scala 2.10 version of the plugin to benefit from the latest fixes? I'm on Scala 2.9.2, Juno + Java 7, and, as you may know, have been persecuted for 3 months now by the sematic highlighting hung thread issue -- completely happy with the IDE otherwise, you guys have made huge progress in the past year -- sematic highlighting itself is a great coding experience enhancement.

Thanks

[iulian dragos]

On Fri, Sep 28, 2012 at 7:47 AM, virtualeyes <sit...@gmail.com> wrote:

Ok, sounds like next year (January or later) then, would be shocked to see Scala 2.10.0 released before then, not even at RC stage yet.

Should we (users of the IDE) be switching to Scala 2.10 version of the plugin to benefit from the latest fixes? I'm on Scala 2.9.2, Juno + Java 7, and, as you may know, have been persecuted for 3 months now by the sematic highlighting hung thread issue

It's hard to debug that without really a reproducible case on our hand. I just pushed a possible fix, can you please upgrade to the latest nightly and let us know if it still happens.

If it still happens, we need all the hints we can get in order to start looking somewhere, so please take some stack traces. To do that, on the command prompt do a 

jps -v

to get the PID of the Eclipse process

when it happens again, switch back to the console and run `jstack <pid>`. Hopefully, if you're fast, we'd get some idea about where it is hanging. :)

iulian

PS. I assume that it works smoothly if you disable semantic highlighting?

 

-- completely happy with the IDE otherwise, you guys have made huge progress in the past year -- sematic highlighting itself is a great coding experience enhancement.

Thanks

On Thursday, September 27, 2012 10:55:15 PM UTC+2, Iulian Dragos wrote:

Hi, feature-wise we are pretty close, but we need to polish the things we have. We also aim to release around the time Scala 2.10.0 is out, and their release date is still unclear. We'll follow up soon.

On Thu, Sep 27, 2012 at 9:26 PM, virtualeyes <sit...@gmail.com> wrote:

I know M2 was delayed, but looking at the road map it appears that worksheet and Juno 4.2 support are the "only" items remaining.

@release date would be a nice to know

Thanks

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

[virtualeyes]

updating now

should note that the hung thread issue, while random, is much more likely to occur when doing several clean/compile cycles or incremental builds via sbt.

For example, when working on a Play 2 Scala project, hung thread is guaranteed to occur at some point during incremental build (~ run) testing; at which point you have to restart the IDE.

I have not disabled sematic highlighting since...I needs it ;-)

I have the nightly in place, will take it for a spin and post back.

Thanks!

On Thursday, September 27, 2012 9:26:08 PM UTC+2, virtualeyes wrote:

[virtualeyes]

k, no luck, semantic highlighting hung thread issue persists after latest update from today.

Here's the jstack dump after it the hung thread occurred (attached)

[iulian dragos]

On Sat, Sep 29, 2012 at 6:33 PM, virtualeyes <sit...@gmail.com> wrote:

k, no luck, semantic highlighting hung thread issue persists after latest update from today.

Here's the jstack dump after it the hung thread occurred (attached)

Unfortunately the latest 2 nightly builds failed, so my fixes were not in there. Can you please update now (I made sure the nightly passed), and try again?

thanks,

iulian

[virtualeyes]

Persists in nightly from today

If it helps, the hung thread seems to occur during cpu intensive activities like incremental builds (play ~run) or when, for example, making a code change in a dependent sbt Project.

Has probably happened on "simple" code changes as well, can't recall, has happened a lot since nightly from @3 months ago.

Did the dump file shed any light on what may be happening?

Thanks

[virtualeyes]

ooooops, wtf, it went away after posting last reply ;-)

That is a first, I'll keep track, would be thrilled if this issue were solved!