Juno M6 Test

[Eric Molitor]

The build at the following site should provide Eclipse Juno M6 compatibility(*). It is based off the platform/juno branch and is built against Juno M6 with a few minor JDT 3.8 changes. Any feedback from adventurous testers is greatly appreciated.

http://scala-ide.s3.amazonaws.com/site.xml

- Eric

(*) it starts and I can create a Scala HelloWorld project.

[Rafał Krzewski]

I've tried it but it did not work too well, unfortunately.

The project builder seemed to work, but all scala files were opened using Java editor resulting in a flood of red squiggles.

I've checked that Open With context menu had both Java editor and Scala editor options present, and Scala editor was selected.

I've also checked 2.1.0-M1 with Eclipse 3.7.2 with the same workspace, and it opened the files in Scala edior without a problem.

regards,
Rafał

[Eric Molitor]

Did this occur when opening an existing Scala IDE project created with a different version of Eclipse? (Trying to consistently reproduce the issue you are seeing)

- Eric

[Rafał Krzewski]

I've opened a workspace created with Eclipse 3.7.1 and Scala IDE 2.0.0 (I think? can't tell exactly), using Eclipse 4.2M6 with experimental Scala IDE.

The errors where also present when I created a new Scala project within this old workspace.

Today I've made another test: I've created a fresh workspace using Eclipse 4.2M6 with experimental Scala IDE. It behaved differently:

- The red squiggles were gone from Scala source files 

- Scala files had [J] icons in package explorer and in the editor tab bar

- Sclaa files that contained objects and traits had Outline view empty, and had no sub-structure visible in Package explorer

- Scala files that contained classes had structure visible in Outline view an in Package explorer

Is there something else I can do to help?

regards,

Rafał

W dniu wtorek, 17 kwietnia 2012 18:19:46 UTC+2 użytkownik Eric Molitor napisał:

Did this occur when opening an existing Scala IDE project created with a different version of Eclipse? (Trying to consistently reproduce the issue you are seeing)

- Eric

On Monday, 16 April 2012 17:19:27 UTC+1, Rafał Krzewski wrote:

I've tried it but it did not work too well, unfortunately.

The project builder seemed to work, but all scala files were opened using Java editor resulting in a flood of red squiggles.

I've checked that Open With context menu had both Java editor and Scala editor options present, and Scala editor was selected.

I've also checked 2.1.0-M1 with Eclipse 3.7.2 with the same workspace, and it opened the files in Scala edior without a problem.

regards,
Rafał

java.lang.Integer

[Eric Molitor]

If you open the Scala menu and select "Run setup diagnostics..." is the "Enable JDT weaving (required for Scala plugin) enabled? 

If you select Window->"Show View"->"Error Log" are there any errors listed?

- Eric

[Rafał Krzewski]

JDT Weaving was off. Somehow I overlooked that, how silly of me.

Allright, now I can play around a little more.

cheers,

Rafal

[Oscar Vargas Torres]

Hi! I'm interested in Eclipse RCP Applications with Java/Scala mixed. I built the Scala IDE (platform/Juno branch) from https://github.com/scala-ide/scala-ide.git (I used build-ide-2.9.x.sh) on Mac OS X Lion (also on ArchLinux).

I've tried a simple E4 application and it works fine when it's run inside the IDE. However, it doesn't work fine when exporting with the Eclipse Product Export Wizard. It seems to be a problem of the build when exporting.


Michel Kraemer wrote an ant script to build Scala projects with Eclipse PDE Build
http://www.michel-kraemer.com/scala-projects-with-eclipse-pde-build-2
however, I don't know ant enough to use this.
-------
I found a something useful here
http://www.assembla.com/wiki/show/scala-ide/Eclipse_Plugin_Development_using_the_Scala_IDE

under
3. Deployment

Workaround: Hidden in the plugin export dialog is an option to "use the class files compiled in the workspace" which circumvents this problem and simply packages you bin/* classes into a plugin.

The only problem is that this option only exists for plugins not for products - so in the case of a product (e.g. an editor application generated from an EMF model) you have to export the product with failures first and then each scala dependend plugin seperately (using the option mentioned above), replacing the corrupt ones in the product.

I've managed to follow this advice, but it seems a little awkward. I'd love to use Scala + Java with Eclipse RCP Applications, and not only Java... Help please!

[Eric Molitor]

I suspect this is not an issue specific to the Juno platform support of the Scala IDE but it does identify a very valid gap. While the project is the "Scala IDE" we can do a better job of documenting how to build and distribute ECP Applications with Scala. Would you mind opening up a ticket?

- Eric

[iulian dragos]

I just gave it a spin and it works quite well! I noticed only one thing: The Scala menu is gone, so I can't open the diagnostics dialog -- but reading this thread it looks like the menu is in place for others. I'll dig around a bit to see why I don't have it.

thanks,

iulian

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

[Eric Molitor]

Just pushed fixes for Juno M7 and RC0. Should hit the update site on the next build.

- Eric

[Eric Molitor]

It also plays nicely with JDK 1.7 :)

- Eric

[Rafał Krzewski]

Hi, I found some time to play with Scala IDE.

I've used JDK 7 u03, Eclipse 4.2 M7 and  Scala IDE build 2.1.0.local-2_09-201204151114-41a2cd3

I'm Maven user so I've coupled that with m2e 1.1.0.20120505-1126, m2eclipse-scala 0.4.0 and Webby 0.2.1.201112101214 (Webby is a m2e extension that runs Servlet applications aka lightweight J2EE without WTP)

My tests application was Lift hello world app generated using Lifty. I have "Mavenized" (created a POM based on SBT build) a while ago so I was importing a Maven project using maven-scala-plugin.

The import worked nicely and I was able to navigate Scala source files in the project, Lift libraries ans Scala standard library quite happily. The project was build cleanly and I was able to launch the application using Webby in a snap.

The only issue I've come across is the debugger: it works extremely slowly. A step over / step into operation can take anything between 10 seconds and 1 minute! 

I was trying to profile it using yourkit profiler. At first glance - there is a lot of actitvity in the presentation compiler thread. I don't know if this is expected during a debugging session and if this is the reason of debugger UI blocking for extended priods of time...

I don't have much time at my hands but if there's someting I can do to help do let me know.

cheers,

Rafal