Scala IDE 4.0-RC1 staged (NOT YET RELEASED)

[Iulian Dragoș]

(this is not an official announcement -- sent only to scala-ide-dev --  please don't tweet. A proper announcement and release notes will follow next week. Now we need to sleep).

It’s my great pleasure to announce that the next major version of the Scala IDE, together with most of its plugin ecosystem (waiting for ScalaTest, and JavaToScala), is staged! It’s been a huge amount of work (almost 1.5 years of development), and particularly the last couple of weeks have been very intense. It’s been amazing to see everyone pushing for making this deadline. Kudos, team! I'd like to particularly thank Simon Schäffer for his amazing work during this time, together with long-time contributor Mirko Stocker and the Typesafe team (Luc, Francois).

tl;dr;

Update site: http://download.scala-ide.org/ecosystem/next/lithium/e44/scala211/dev/site/
Scala IDE download:

linux.gtk.x86.tar.gz
linux.gtk.x86_64.tar.gz
macosx.cocoa.x86.zip
macosx.cocoa.x86_64.zip
win32.win32.x86.zip
win32.win32.x86_64.zip

MultiVersion Scala support

That’s right. Finally, you can have projects with different versions of Scala in the same workspace. Thanks to Francois and the Scala team for making the language-level flags a reality: the IDE can now ship on a single Scala version, but support both 2.10 and 2.11 projects.

ScalaDoc support

We have it at last! Right now it only works for Scala source code (but it works with attached sources!). And it's not your daddy's javadoc! It respects Scala semantics, have a look at the collection library to see all of them in action (inherited, variable substitution, overloading…). Again, Francois was the driving force behind this one, but Eugene Vigdorchik laid the ground work (excellent work too!), and Simon made the hovers beautiful. There’s even CSS you can tweak yourself!

Save Actions

Scala-specific save actions, Simon's Google Summer of Code project. We start small with just a few simple ones until we iron out all the details. Matthias Langer is getting up to speed and decided to help with Save Actions, so expect more of that soon.

Less memory consumption!

Another great contribution.Thanks to the Virtus guys we have a watchdog that shuts down compilers that haven’t been used in a while. This can dramatically decrease memory consumption if you have many open projects.

A Scala-specific Solarized Light theme!

Not Darcula, it’s even better! We’ll include this in the pre-packaged bundle as an option (but not the default).

This release includes a ton of other tweaks, both in performance and correctness, editor improvements and smarter hovers. We’ll prepare a more detailed description for the release notes next week.

Since this is a huge release, please give it a spin and report bugs or regressions.

And, since without a screenshot it didn't happen.. here's a screenshot.

​

-- 

--
Iulian Dragos

------
Reactive Apps on the JVM
www.typesafe.com

--

--
Iulian Dragos

------
Reactive Apps on the JVM
www.typesafe.com

[Chee Seng Chua]

Hi Iulian, 

I am building ScalaTest plugin for this, built fine using the following update sites: 

http://download.scala-ide.org/ecosystem/next/lithium/e44/scala211/dev/site/

http://download.scala-ide.org/ecosystem/next/lithium/e38/scala211/dev/site/

However, when I am trying with a fresh kepler to install Scala IDE using http://download.scala-ide.org/ecosystem/next/lithium/e44/scala211/dev/site/ , it seems to get this error:

Cannot complete the install because one or more required items could not be found.

  Software being installed: Scala IDE for Eclipse dev support 4.0.0.rc1-2_11-201410101606-7b622ed (org.scala-ide.sdt.dev.feature.feature.group 4.0.0.rc1-2_11-201410101606-7b622ed)

  Missing requirement: Scala Plugin 4.0.0.rc1-2_11-201410101606-7b622ed (org.scala-ide.sdt.core 4.0.0.rc1-2_11-201410101606-7b622ed) requires 'bundle org.eclipse.jdt.core [3.10.0,4.0.0)' but it could not be found

  Cannot satisfy dependency:

    From: Scala IDE for Eclipse dev support 4.0.0.rc1-2_11-201410101606-7b622ed (org.scala-ide.sdt.dev.feature.feature.group 4.0.0.rc1-2_11-201410101606-7b622ed)

    To: org.scala-ide.sdt.core 0.0.0

Is that expected and I can upload my combined update site?

Thanks.

Chee Seng

[iulian dragos]

Chee Seng, thanks for reporting. That's definitely not expected, it seems the Luna build ended up in the Kepler update site.

--
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/c2bb1aba-26f1-46af-8207-6ff87a7736a7%40googlegroups.com.

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

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

[Chee Seng Chua]

Hi Iulian, 

I see, is it fixed now?  please let me know when it is fixed, so that I could rebuild and try again.

Thanks.

Chee Seng

[Luc Bourlier]

Hey Chee Seng,

There are 2 builds of Scala IDE, one for Kepler, one for Luna, due to one incompatibility. For Kepler, the update site is http://download.scala-ide.org/ecosystem/next/lithium/e38/scala211/dev/site/ . I double checked, the dependency is correct there.

Luc

[Chee Seng Chua]

Hi Luc, 

I just try again and the e38 one seems to be working, but when I tried to build with e44 for luna: 

http://download.scala-ide.org/ecosystem/next/lithium/e44/scala211/dev/site/

I got error like this: 

[ERROR] Cannot resolve project dependencies:

[ERROR]   Software being installed: org.scala-ide.sdt.scalatest 2.9.3.qualifier

[ERROR]   Missing requirement: org.scala-ide.sdt.core 4.0.0.rc1-2_11-201410101606-7b622ed requires 'bundle org.eclipse.jdt.core [3.10.0,4.0.0)' but it could not be found

[ERROR]   Cannot satisfy dependency: org.scala-ide.sdt.scalatest 2.9.3.qualifier depends on: package org.scalaide.core 0.0.0

[ERROR] 

[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.jdt.core 3.9.0.v_OTDT_r220_201306071800 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.eclipse.jdt.core 3.9.1.v_OTDT_r221_201309101918 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.eclipse.jdt.core 3.9.2.v_OTDT_r222_201402180730 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.scala-ide.sdt.core 4.0.0.rc1-2_11-201410101606-7b622ed to bundle org.eclipse.jdt.core [3.10.0,4.0.0).", "No solution found because the problem is unsatisfiable."] -> [Help 1]

org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.jdt.core 3.9.0.v_OTDT_r220_201306071800 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.eclipse.jdt.core 3.9.1.v_OTDT_r221_201309101918 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.eclipse.jdt.core 3.9.2.v_OTDT_r222_201402180730 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.scala-ide.sdt.core 4.0.0.rc1-2_11-201410101606-7b622ed to bundle org.eclipse.jdt.core [3.10.0,4.0.0).", "No solution found because the problem is unsatisfiable."]

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)

Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.jdt.core 3.9.0.v_OTDT_r220_201306071800 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.eclipse.jdt.core 3.9.1.v_OTDT_r221_201309101918 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.eclipse.jdt.core 3.9.2.v_OTDT_r222_201402180730 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.scala-ide.sdt.core 4.0.0.rc1-2_11-201410101606-7b622ed to bundle org.eclipse.jdt.core [3.10.0,4.0.0).", "No solution found because the problem is unsatisfiable."]

at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98)

at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)

at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)

at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:126)

at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:81)

at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:374)

at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:350)

at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)

at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)

... 11 more

It seems weird to me for org.scala-ide.sdt.core 4.0.0.rc1-2_11-201410101606-7b622ed to require bundle org.eclipse.jdt.core [3.10.0,4.0.0), no?

Thanks.

Chee Seng 

[Luc Bourlier]

Le lundi 20 octobre 2014 06:25:48 UTC+2, Chee Seng Chua a écrit :

Hi Luc, 

 

It seems weird to me for org.scala-ide.sdt.core 4.0.0.rc1-2_11-201410101606-7b622ed to require bundle org.eclipse.jdt.core [3.10.0,4.0.0), no?

No, it is normal, jdt (like a lot of the other features) never made the jump to 4.x. The version of jdt in Juno in 3.8.x, in kepler 3.9.x and in Luna 3.10.x.

I tested your build from the 'kepler-nightly-2.11' branch, with the reference to the Eclipse Luna p2 repo uncommented, and it worked fine. Are you using an other branch?

Luc

 

Thanks.

Chee Seng

 

[Chee Seng Chua]

Hi Luc, 

Uncommenting the Luna P2 repo did the trick, it builds successfully now and I uploaed the combined site to the normal place: 

http://www.artima.com/newplugins3/combined

Hopefully it will get pulled into Scala IDE update site soon.

Thanks for your help!

Chee Seng

[iulian dragos]

I manually started the ecosystem build, so if all is OK it should appear in the update site in the next hour.

iulian

--

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/b2454cfb-71a0-4e5d-b1d2-afd45dbe4f1d%40googlegroups.com.

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

[iulian dragos]

It didn't pick it up, but unfortunately I can't debug it... also, the server won't let me check what's at that URL (it appends index.jsp instead of showing me the directory listing).

[Chee Seng Chua]

Hi Iulian, 

Bummer, hmm, I wonder if you can download the combined site directly to try pulling from that and see what's wrong?  You can download the combined site here: 

http://www.artima.com/newplugins3/combined.tar.gz

Hope it can tells what went wrong.

Thanks!

Chee Seng

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/CAOwe9fb2MR702PPuvOCAsThwp8WvSEzfMxeM2QcmhRWNpf1esw%40mail.gmail.com.

[Luc Bourlier]

Hi Chee Seng,

Because we now have an API in Scala IDE, we were able to relax the rules on linking plugins to a version of Scala IDE. A rebuild of the plugins will only be required for major version change of Scala IDE, or major version change of Scala library, or on any version change of the Scala compiler (no API at this level).

But it also means a few configuration changes, that I haven't had the time to document it yet. I made a branch with the  changes needed to make your plugin work well with the new dependency checks: https://github.com/skyluc/scalatest-eclipse-plugin/commits/issue/new-dependencies-rules

Luc

[Chee Seng Chua]

Hi Luc, 

I pulled your changes in (and updated my build-tool to master, 0.5.1), but hit with another problem when trying to build for kepler (http://download.scala-ide.org/sdk/lithium/e38/scala211/dev/site), it hit the following compilation error when building: 

[ERROR] /home/cheeseng/Desktop/test/scalatest-eclipse-plugin/org.scala-ide.sdt.scalatest/src/scala/tools/eclipse/scalatest/ScalaTestImages.scala:40: error: object ScalaImages is not a member of package org.scalaide.ui

[ERROR] import org.scalaide.ui.ScalaImages

[ERROR]        ^

[ERROR] /home/cheeseng/Desktop/test/scalatest-eclipse-plugin/org.scala-ide.sdt.scalatest/src/scala/tools/eclipse/scalatest/ScalaTestImages.scala:80: error: not found: value ScalaImages

[ERROR]         ScalaImages.MISSING_ICON

[ERROR]         ^

[ERROR] /home/cheeseng/Desktop/test/scalatest-eclipse-plugin/org.scala-ide.sdt.scalatest/src/scala/tools/eclipse/scalatest/launching/ScalaTestFinder.scala:39: error: object IScalaPresentationCompiler is not a member of package org.scalaide.core.compiler

[ERROR] import org.scalaide.core.compiler.IScalaPresentationCompiler

[ERROR]        ^

[ERROR] /home/cheeseng/Desktop/test/scalatest-eclipse-plugin/org.scala-ide.sdt.scalatest/src/scala/tools/eclipse/scalatest/launching/ScalaTestFinder.scala:40: error: object IScalaPresentationCompiler is not a member of package org.scalaide.core.compiler

[ERROR] import org.scalaide.core.compiler.IScalaPresentationCompiler.Implicits._

[ERROR]                                   ^

[ERROR] /home/cheeseng/Desktop/test/scalatest-eclipse-plugin/org.scala-ide.sdt.scalatest/src/scala/tools/eclipse/scalatest/launching/ScalaTestFinder.scala:46: error: object IScalaPlugin is not a member of package org.scalaide.core

[ERROR] import org.scalaide.core.IScalaPlugin

[ERROR]        ^

Shouldn't the luna and kepler version supports the same new set of API?

Thanks!

Best Regards, 

Chee Seng 

--
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/70d3aa04-2fec-43e7-bee6-15d75e2a8598%40googlegroups.com.

[Luc Bourlier]

Hi Chee Seng,

I could reproduce your problem. It is linked to the fact that the p2 dependency resolution in tycho might not always choose the latest version available of a plugin as the 'best' one. So it was picking up sdt.core 4.0.0-m3 instead of 4.0.0-rc1 (only the qualifier is different, so it assumes there are no major differences ...).

The solution is to require at least an rc version by changing the version range in org.scala-ide.sdt.scalatest/META-INF/MANIFEST.MF by:

org.scala-ide.sdt.core;bundle-version="[4.0.0.rc,5.0.0)",

HTH,

Luc

[Chee Seng Chua]

Hi Luc, 

The fix works!  I have rebuilt the combined site and uploaded to the usual url: 

http://www.artima.com/newplugins3/combined

Hopefully it will get picked up correctly this time!

Thanks!

Best Regards, 

Chee Seng

--
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/6cffb040-7232-4762-bb8e-7d01ab1a3b7b%40googlegroups.com.

[Luc Bourlier]

It is being picked up. I launched an ecosystem build.

Luc

Le mardi 28 octobre 2014 15:45:53 UTC+1, Chee Seng Chua a écrit :

Hi Luc, 

[Chee Seng Chua]

Hi Luc, 

Just tested and it is working!

Thanks!

Best Regards, 

Chee Seng

--
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/89b3cec2-0c4b-4950-b594-c3579ffefbb9%40googlegroups.com.

[iulian dragos]

Hi Chee Seng,

Could you please re-build scalatest for Luna/Kepler? Since RC2 is using the new Scala 2.11.4, you need to have a rebuild (since the Scala *compiler* does not guarantee any binary compatibility, only at the library level). Once this is correctly picked up, you won't need to re-publish ScalaTest for additional IDE releases in the 4.x series.

thanks,

iulian

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/CANPJY7pJtAjzS_Wcoxq3hiQ0AmexvjH0_ozgTuca%3Dc3BufSXhQ%40mail.gmail.com.

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

[Chee Seng Chua]

Hi Iulian, 

I rebuilt and upload it to (not the usual url, since RC2 is not out yet):

http://www.artima.com/newplugins3/combined-next

Can you check if it can be picked up correctly?

Thanks.

Chee Seng

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/CAOwe9fYGFKm0P_zBRhsKqufAAYVfhTUhP3k3fhWm1q1uu-4skA%40mail.gmail.com.

[iulian dragos]

It's there, thank you!

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/CANPJY7qtC%2Bc9QS7ojNcAP2WLtbpjsqgGfZciQ5wZvxspP44cCg%40mail.gmail.com.

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

[Bill Venners]

Hi Iulian,

We had a report today of someone getting this error message from eclipse about SuperSafe:

I purchased the SuperSafe Scala compiler plugin from Artima and when I use it in my SBT / Eclipse projects (via sbt-eclipse) with the latest version of the language (v 2.11.7), I get a cross-compile error, specifically: "Compiler plugin supersafe_2.11-1.0.4.jar is cross-compiled with incompatible version for this project: 2.11.0 vs 2.11.7". When I compile from within SBT I don't see the error. Any ideas how to beat Eclipse into submission for it not to complain? I'm using Eclipse Mars.1 (release 4.5.1) with scala-ide v 4.2.0-vfinal-2_11....

We are trying to reproduce it now, but I thought I'd ask whether that looks familiar at all to you. Is there a reason a compiler plugin compiled for 2.11.0 would not work with 2.11.7, with or without Eclipse?

Thanks.

Bill

--

Bill Venners
Artima, Inc.
http://www.artima.com

[Simon Schäfer]

On 10/14/2015 11:03 PM, Bill Venners wrote:

Hi Iulian,

We had a report today of someone getting this error message from eclipse about SuperSafe:

I purchased the SuperSafe Scala compiler plugin from Artima and when I use it in my SBT / Eclipse projects (via sbt-eclipse) with the latest version of the language (v 2.11.7), I get a cross-compile error, specifically: "Compiler plugin supersafe_2.11-1.0.4.jar is cross-compiled with incompatible version for this project: 2.11.0 vs 2.11.7". When I compile from within SBT I don't see the error. Any ideas how to beat Eclipse into submission for it not to complain? I'm using Eclipse Mars.1 (release 4.5.1) with scala-ide v 4.2.0-vfinal-2_11....

We are trying to reproduce it now, but I thought I'd ask whether that looks familiar at all to you. Is there a reason a compiler plugin compiled for 2.11.0 would not work with 2.11.7, with or without Eclipse?

Yes, there is. The API of the compiler (where a compiler plugin depends on) is not binary compatible among minor releases, only the stdlib is. Therefore the error message is correct. You need to cross compile SuperSafe against all minor releases of 2.11 (+2.10 if that has to be supported too).

Simon

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/CAO_RykpE5ys_fMpEbmD2ZFEf6%2BDkLricS8rmr8kaov2qerx_jQ%40mail.gmail.com.

[iulian dragos]

On Wed, Oct 14, 2015 at 11:17 PM, Simon Schäfer <ma...@antoras.de> wrote:

On 10/14/2015 11:03 PM, Bill Venners wrote:

Hi Iulian,

We had a report today of someone getting this error message from eclipse about SuperSafe:

I purchased the SuperSafe Scala compiler plugin from Artima and when I use it in my SBT / Eclipse projects (via sbt-eclipse) with the latest version of the language (v 2.11.7), I get a cross-compile error, specifically: "Compiler plugin supersafe_2.11-1.0.4.jar is cross-compiled with incompatible version for this project: 2.11.0 vs 2.11.7". When I compile from within SBT I don't see the error. Any ideas how to beat Eclipse into submission for it not to complain? I'm using Eclipse Mars.1 (release 4.5.1) with scala-ide v 4.2.0-vfinal-2_11....

We are trying to reproduce it now, but I thought I'd ask whether that looks familiar at all to you. Is there a reason a compiler plugin compiled for 2.11.0 would not work with 2.11.7, with or without Eclipse?

Yes, there is. The API of the compiler (where a compiler plugin depends on) is not binary compatible among minor releases, only the stdlib is. Therefore the error message is correct. You need to cross compile SuperSafe against all minor releases of 2.11 (+2.10 if that has to be supported too).

That's the reason why we enable these checks by default, but they can be disabled. You can go to Project Properties -> Scala Compiler -> Build Manager and uncheck "withVersionClasspathValidator" (might require a clean build, not sure).

iulian

 

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/561EC65C.2010609%40antoras.de.

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