I am using STS based on eclipe 2.6.2 and there is a scala plugin for eclipse
http://www.assembla.com/wiki/show/scala-ide
but it is not compatible with STS.
Is there anything other plugin.
I mainly need it debug play framework scala projects.
The Eclipse IDE for Scala should work with STS. I just tried it with version 2.6.1.RELEASE (build id 201105041000).
Make sure you do not select JDT Weaving for Scala when installing the Scala plugin. The JDT weaving component is provided already by STS (albeit an older version). The Scala plugin comes with a newer version, that upsets the AspectJ plugin (included by STS).
Even easier, you can use the Dashboard view, 'Extensions' page. You can check the Scala IDE from there, and it correctly leaves out the JDT weaving plugin.
If you have any other issues, use the mailing list (scala-ide-user#googlegroups.com) or file a ticket.
Related
I have the task to do some work on our GWT 2.2 code base with
the GWT Config, etc, used, is long gone. And I must use Eclipse Kepler.
Does current GWT provide backward compatability that far?
Any thoughts?
The version of the Eclipse plugin is independent of the version of the SDK you use in your project. You can use the newest plugin with GWT projects that needs older versions of the SDK.
You have to set this up in the project properties.
Does anyone know where I can find the most recent feature comparison document for Spring IDE plugin vs SpringSource Tool Suite STS (version 3.3.0)?
I believe Eclipse made some good progress in Kepler release, (for example Maven support being shipped in) so was wondering if the feature gap between Eclipse+Spring IDE plugin and STS highlighted in 2.9.2 Feature Comparison were reduced in Eclipse Java EE Kepler.
There is not much difference now between Eclipse + Spring-IDE and STS. The main difference is that when you download STS, you are guaranteed that all the bits and pieces work together. When you install Eclipse + Spring-IDE, you may have some compatibility problems and trouble installing or upgrading.
My advice is this: if you already have an Eclipse that has custom plugins installed, then go with Eclipse + Spring-IDE and if you are starting from scratch, go with STS.
I installed scala-IDE 3.0 on my Linux VM and after the installation the new version converted all my scala projects to 2.10.0. How do I manage the scala version from eclipse on a project by project basis. scala-IDE 3.0 is claimed to be both 2.9.2 and 2.10.0 compatible though through different update sites:
3.0.0 Release
This release is available for both Scala 2.9 and Scala 2.10, and both Eclipse 3.7 (Indigo) and Eclipse 3.8/4.2 (Juno), through different update sites.
At the moment (May 23, 2013), you can only have one Scala IDE plug-in per Eclipse intallation. Hence, if some of your projects are on Scala 2.9, while others are on Scala 2.10, you will need to use two different Eclipse installations, with the right Scala IDE plug-in installed.
We are aware that this isn't ideal, and we are actively working to remove this limitation.
The best workaround I can offer you at the moment is to use the pre-packaged Scala IDE SDK, which is available for both Scala 2.9 and Scala 2.10. This way you don't have to waste time setting up Eclipse for Scala development.
strong texti have a very simple eclipse 3.8-based rcp application with an .aj file. i also have AJDT 2.2.1 installed, and have the following four entries in my build.properties:
javacSource=1.6
javacTarget=1.6
compilerAdapter=org.eclipse.ajdt.core.ant.AJDT_AjcCompilerAdapter
sourceFileExtensions=*.java, *.aj
i am using a headless build approach via Ant, and it has been working like a charm, AJDT and all, while using java 1.6. but once i upgraded from java 1.6 to 1.7, and changed the two aforementioned build.properties entries' -- javacSource and javacTarget -- values from 1.6 to 1.7, i got a boat-load of build errors, all with the following suffix:
... are only available if source level is 1.5 or greater
setting build.properties' javacSource back to 1.6, while leaving javacTarget at 1.7 works. or if i were to comment out the two AJDT-specific entries from my build.properties, while leaving javacSource and javacTarget values at 1.7. the build completes just fine as well. so my guess is that AJDT compiler is somehow the culprit. the question is why and what can be done to resolve it.
thank you for your time!!!
It sounds like one of two things:
Your AJDT installed does not have an AspectJ in it that is compatible with Java 1.7. What AspectJ version are you building with? Note that this aspectj version may be different from the one in your target platform.
You are not correctly specifying the Java source/target version in a way that AspectJ can recognize. How are you specifying the Java source/target version?
I found a problem using scala-ide 2.1.0 m2.
I'm developing a java/ scala mixed project. When I add a method in java class and call it in scala. Scala Ide will report an error that the method doesn't exists. I tried to refresh the project but I got no luck. I have to restart Eclipse(3.7 indigo) to let scala IDE load the updated java class.
Is there any way to let scala IDE recognize java changes without restarting eclipse?
Cleaning the project works for me in same situation.
Scala IDE is improving quite a lot lately. I had few problems mixing java and scala in one Eclipse project (generated by SBT, but not very relevant for this question) using the latest Eclipse IDE (Juno) and the latest version of Scala IDE.
I'd advise to download the latest version of Eclipse and and install the latest version of the Scala IDE.