How can I help?

[Eugene Melekhov]

Hi, 

My name is Eugene, I am an old Java developer. I heard about Scala about five years ago, it seemed very promising, but unfortunately I was unable to look at the details at that moment.

Recently I've found some time to really read about Scala, watch some Scala Days presentations etc and I have to admit that five years ago I missed  really great language :-)  !

So, I decided to study it and hopefully use it in my day-to-day work in the future."Programming in Scala" by Martin Odersky is great, I really enjoy reading it and playing with code samples, but I'm thinking about doing something useful. 

I found out that Scala IDE is a bit outdated and is losing it's popularity among Scala developers which is a pity. I've been using Eclipse for a very long time and I worked on Eclipse plugins in the past, so I could probably help.

Since I am Scala newbie I'd like to start fixing some small relatively easy issues just to become familiar Scala, Scala IDE architecture, code base etc. But I'd like to know about the future plans as well.

So, here are some questions to the Scala IDE developers:

1. What is going on in Scala IDE project? Are you going to continue it or abandon since most Scala developers prefer Idea, VS Code, Ensime etc.

2. Since dotty and Scala 3 are gaining traction it would be very desirable to support it in Scala IDE.  As far as I understand it is not a trivial task since language and compiler undergo serious changes. Are there any plans for that support?

3. Any other major changes/ideas?

Thank you.

--

Eugene Melekhov

[Simon Schäfer]

scala-ide is no longer officially developed. All of the former core devs moved on to different projects. I suggest to start contributing to the sbt ide integration, the scalameta metal project or the dotty ide integration, where all of the current devs are working on. Just asks the devs there where you could work on.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

--

You received this message because you are subscribed to the Google Groups "Scala IDE Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/1a93738d-9ee9-41e7-994a-8588397dccd4%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Scott Carey]

I'd love an explanation on how any of those can help my use case.

I have some pure scala projects, in sbt.  Sure, that is easy.

But I have big legacy stuff with mixed scala/java + maven.  Is IntelliJ the only remaining tool that can handle this (with Java 9+)?

[Simon Schäfer]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Friday, 21. September 2018 01:48, Scott Carey <scott...@gmail.com> wrote:

I'd love an explanation on how any of those can help my use case.

I have some pure scala projects, in sbt.  Sure, that is easy.

But I have big legacy stuff with mixed scala/java + maven.  Is IntelliJ the only remaining tool that can handle this (with Java 9+)?

yes, probably. the latest scala-ide should still work though if you don't use the latest Scala version.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/48d48295-e908-4929-83ff-f933e7362230%40googlegroups.com.

[Eugene Melekhov]

I've been using Eclipse since v 1.0 and have some thoughts:

• Eclipse is a bit too complex for relatively small and mono language projects. In such cases some people tend to use "light" tools like Idea, VsCode, Vim, Emacs etc. Most likely it's matter of taste.
  
• Eclipse is not that good at projects with external build systems like maven or sbt for example. Yes, maven support has improved a lot over the past years, but still it is not that seamless as we would like it to be
  
• Eclipse is really great for big complex multi language multi platform projects with lot of various different tools involved. I don't know any other IDE or combination of tools that gives that power.
  

What is important is that Eclipse was designed exactly for the latter case and making Eclipse plugin for language support is not the same as merely adding syntax highlighting and possibility to call maven/sbt whatever.

And as result creating and supporting a good language design tool plugin is really hard work. JDT, CDT are huge projects with lot of developers working on them for many years

So,in my humble opinion Scala development tool plugin is really needed. Most likely it should be based on language server protocol in order to reduce the efforts on that part. 

Ensime , scalameta/metals could be used for scala 2.x  and Dotty already has language server.

So I hope that this project will reborn in the future, or at least cold be used as the base for the new great plugin

Sorry for so long rant :-) hope you have read until this line

[Scott Carey]

On Friday, September 21, 2018 at 7:35:01 AM UTC-7, Simon Schäfer wrote:

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Friday, 21. September 2018 01:48, Scott Carey <scott...@gmail.com> wrote:

I'd love an explanation on how any of those can help my use case.

I have some pure scala projects, in sbt.  Sure, that is easy.

But I have big legacy stuff with mixed scala/java + maven.  Is IntelliJ the only remaining tool that can handle this (with Java 9+)?

yes, probably. the latest scala-ide should still work though if you don't use the latest Scala version.

Definitely not, that is why I'm asking.

Photon 'works' with Scala IDE, in that it builds and loads projects fine.  But it throws popup errors on typing, as auto completion crashes.  It couldn't be more unusable than triggering a popup every few keys typed.

[Scott Carey]

On Friday, September 21, 2018 at 11:27:34 PM UTC-7, Eugene Melekhov wrote:

I've been using Eclipse since v 1.0 and have some thoughts:

• Eclipse is a bit too complex for relatively small and mono language projects. In such cases some people tend to use "light" tools like Idea, VsCode, Vim, Emacs etc. Most likely it's matter of taste.
  
• Eclipse is not that good at projects with external build systems like maven or sbt for example. Yes, maven support has improved a lot over the past years, but still it is not that seamless as we would like it to be
  

Works fine.  100+ maven modules using M2e, no problems in recent versions.  Works better than IDEA here.  Auto-detection of pom changes works better, IDEA users have more 'strange' classpath issues with two versions of the same artifact in scope sometimes.