I have a simple question regarding groovy with eclipse. I downloaded the plugin as mentioned and i didnt have problems with installations but i have compiler errors in hello p. the problem in my opinion that eclipse isnot using the groovy compiler. but i have no idea what to do
Is the filename extension .groovy?
Are you sure the project has the Groovy nature? (right-click on the project, and ensure Remove Groovy Nature appears. If Add Groovy nature appears, then the project doesn't have a groovy nature, and therefore the groovy compiler won't work).
Could you also post the file that isn't compiling. There might be something wrong with what you typed.
Make sure you are opening the file in a Groovy editor.
Look for any exceptions in your error log.
Also, just in case, you can try uninstalling and reinstalling the plugin. I'd recommend using the latest milestone version as that one is about to be promoted to 2.1.2 final.
http://dist.springsource.org/milestone/GRECLIPSE/e3.6/
I confirmed that Groovy plugin isnot workingn on mac. I tried it on 2 machines and they are giving the same error. Groovy plugin is working on windows without problems :)
NetBeans is a better option for Groovy+Java development. You can mix Java and Groovy files in a Java project in NetBeans. It also creates a distributable jar for your project. No classpath and jar issues with NetBeans created MET-INF file.
Related
Is there a way to configure AEM into an IDE like IntelliJ,Eclipse...
So that the IDE shows the errors on my project before I compile it even if I put it outside the source folder like for example the components created.
If possible both the .java and .jsp
I'm not entirely sure what you mean by outside the source folder, but have you taken a look at adobe's documentation?
They have instructions for IntelliJ + AEM with Maven. It also instruct on jsp support as well. It's for 5.6.1 but it should be valid for 6.x as well.
https://docs.adobe.com/docs/en/cq/5-6-1/developing/developmenttools/howto-develop-aem-projects-with-intellij.html
Here's one for Eclipse
https://helpx.adobe.com/experience-manager/using/creating-aem-project-using-eclipse.html
They also have a more generic set of instruction
https://docs.adobe.com/docs/en/cq/5-6-1/developing/developmenttools/how-to-build-aem-projects-using-apache-maven.html#How-To%20Work%20with%20JSPs
Yes, you can maintain CRX data(AEM folders like /etc, /apps, /content, etc) in an IDE like eclipse. This will help you iron out all the compilation errors using features of IDE. Make use of this eclipse plugin called vaultclipse. You can install it from eclipse marketplace.
There is also another plugin called AEM plugin, details on how to use it here.
While trying to run Jython Scripts in Eclipse using PyDev, I noticed that the Jython run configuration was not pulling the java classpath value from maven/m2eclipse.
Has anybody configured eclipse so that PyDev pulls the correct classpath from maven?
Notes:
I can in fact run jython scripts, and import classes from the jre, but my maven dependencies do not appear on the classpath when interpreting the Jython scripts
I have seen the question/answer Using Jython with M2Eclipse and have used maven plugins to execute jython scripts, but that is not what I am interested in
Thank you all.
Update: Looking at extending PyDev plugin to initialize jython run configurations with the project classpath (containers). Trying to figure out which extensions I have to depend on to get access to the .classpath file.
Update: Figured what I need to change and how. Working on it now.
Someone Else Seems to have the same problem, and may have solved it: https://github.com/Kbrowder/PyJDT
Edited: Posted Prematurely, updates
Turns out Someone has already written an eclipse plugin to solve this exact problem.
The plugin is called PyJDT: https://github.com/Kbrowder/PyJDT
Tested it on Eclipse Juno with PyDev.
Thank you K. Browder
I'm trying out 'Play Framework 2.0' on Scala IDE plugin 2.0, for Eclipse Helios (fully supported by Scala IDE plugin).
When I create a play application and choose Scala template, it does work. That is,"play run".
When running 'play eclipsify' and then importing the project into Eclipse, I am getting errors. Any ideas?
The screenshot reveals that you're in the Java Perspective. Go to Window - Open Perspective - Other... and pick Scala.
When you create a new Scala project, eclipse asks you to switch perspective. If you import an existing project however, it doesn't. I filed an enhancement request.
On the Scala IDE website there is a tutorial on how to configure the Scala IDE to do development with play2.0:
http://scala-ide.org/docs/tutorials/play20scalaide20/index.html
Follow the steps there and if it doesn't work please report issues to the tutorial's author or in the scala-ide-user ML.
By the way, I don't believe that changing Perspective will make any difference. The Eclipse perspectives are purely UI changes, the underlying behavior should not be affected.
I was waiting, hoping someone more knowledgeable would answer...
I'd look at the .project file for your messed-up project, compare it with a correct one, and hack the messed-up one as appropriate. I wish I could be more specific. I'd guess that the problem is in the <buildSpec> or <natures> section of the file.
You may want to back up the .project file up first. Make sure the project isn't open in Eclipse while you're editing it.
Right click your project, Configure > Add Scala Nature
I installed Eclipse Java-EE edition instead of standard Java Edition, and all works now.
I haven't gone back to repeat with standard Java Edition to confirm, but seems to only work with EE edition.
I am giving a try to Scala Eclipse IDE after a very long time. I installed Eclipse and the said Scala plugin only a while ago, but I am unable to get stuff working. In all of the Scala files, I get the errors like following (See the tooltip):
This project uses Gradle for building, and I also have the latest version of Groovy plugin installed. Please help me get this thing working. Thanks.
Edit:
Thank you, everyone. The problem was solved. It appears there was a problem with my Scala plugin installation. A complete reinstall of everything (including Eclipse) helped. Also, this time I did not install the Groovy plugin.
I don't know which version of Eclipse / Scala-IDE you're using, but there are two reasons I know this sometimes happens:
1) You don't have JDT weaving for Scala installed.
The scala-ide uses aspects to weave in code into the JDT compiler. If you don't have this installed, this may cause the Scala files to be seen as Java files.
2) If, somehow, the Java Source File content type includes *.scala. In fact, it should be Scala Source File. If this is the case, you should remove the *.scala from the Java Source File content type.
I have installed latest scala ide plugin to eclipse (Version: 3.4.2). It seems installation is ok without any errors.
I am able to create a scala project and add a package, but i couldn't add scala object, at the time it shows "projectname" is not a Scala project error message in add object dialog.
I have googled and found it could be related to JDT Weaving not enabled in eclipse. I have verified, its enabled and running in my environment.
Below the screenshot of the error.
alt text http://a.imageshack.us/img80/3070/scala.png
I just started scala.. Can someone help me to resolve this problem?
I had a similar error two minutes ago. Here's how I fixed it. I'm using Helios and the relevant Scala IDE version.
Right click on the project name --> Configure --> Add scala nature
I must mention that I have the M2Eclipse plugin as well and my project is a Maven project in addition to having a Scala "nature" .. Not that it should matter .. ;-)
The error message means your project is not recognize as a Scala one (as detailed in the scala.tools.eclipse.wizards.AbstractNewElementWizardPage.scala class.
But adding "Scala nature" to your project, as suggested by Alexey Romanov in the comments, might not be enough in this case.
The requirements mentioned in scala-ide.org clearly include:
Java Developer Toolkit 1.6
Eclipse Classic 3.5.2
So could you try with a more recent Eclipse version?
See Requirements and Installation, and then the turorial:
As mentioned, note the 'S' in the Scala project icon.