More often when I install a plugin, doesn't recognize it.
For example using Joda Time, I have a variable LocalDateTime date (i'm importing joda library) and eclipse says unable to resolve class LocalDateTime, though the application works.
Or I have installed the grails icepush plugin but after the installation taglib files were missing.
It's a SpringSource problem?
You should upgrade to SpringSource Tool Suite (STS) which is Eclipse bundled with a suite of plugins. It has great support for Groovy and Grails. 2.5.0 was recently released and it has a plugin wizard for installing, updating, and uninstalling plugins, although it supports plugins installed from the commandline too. I find I sometimes need to manually refresh it but that's simple - just right-click on the project and select Grails Tools | Refresh Dependencies.
After installing you'll need to add support for Groovy and Grails - that's available from the Dashboard.
Download from http://www.springsource.com/developer/sts
You are not doing anything wrong, chances are the eclipse toolset is still behind the competition. As mentioned by #Burt, you can get the STS from SpringSource directly or you can get IntelliJ IDEA which also has a very good clean interface to Grails applications. The latest 9.0.3 works very well with large, complex Grails applications, and seems to have a very advanced intellisense (autocomplete) capabilities.
Related
I have been learning Groovy/Grails Tool Suite (GGTS) 3.6.4, with Grails 2.4.4 using some video tutorials. When I attempt to package the project into an application using the grails war command on the Windows command prompt, I get the following error:
"Error Gradle build terminated with error: Task 'assemble' not found in root project ..."
Any references to this error that I have found online have only involved Android Studio (for instance), so I am at a loss here as to how to fix it for GGTS.
I have Android Studio 1.0.1 installed, and in case it was affecting the Grails packaging, I tried the solution of removing the <component name="FacetManager"> from the general Android Studio "MyApplication.iml" file, but that had no effect. I couldn't find any analogous file for the GGTS.
In case the issue lies elsewhere in my overall installation, I have Java JRE 7_79 (64-bit) installed, as well as the the JDK 1.7.0_79 (64-bit)
OK. I found out what the cause of the error was, and how to avoid it in the future.
The Problem
Grails 3.0.1 requires the following files for grails war to work:
build.gradle
gradle.properties
gradlew
gradlew.bat
\gradle (directory)
Grails 2.4.4 does not require any of the above files for making a WAR file.
GGTS 3.6.4 does not work with Grails 3.0.1, but it comes with and works fine with Grails 2.4.4.
The Solution
Copying the stated Gradle files & directory to a GGTS project folder fixed the problem. However, I wasn't satisfied with needing to do this manually or with a custom batch file for every project.
Looking deeper, it turns out that when working out compatibility issues between the Java 32-bit JRE existing on my system and the Java 64-bit JRE & SDK, Grails, and GGTS versions (there was a lot of fiddling to get things working), at one point I had set up my global variable to Grails to be directed at 3.0.1, and I failed to update it to Grails 2.4.4. Making this change has fixed the issue.
Explaining the Cause
When following this video series on installing a compatible set of Java, Grails, and GGTS, the instructor manually downloaded the latest version of Grails from the Grails site and then downloaded GGTS separately from its own site. Both of these were older versions than what I was working with.
In my case it turns out that, after setting up the Java SDK & Grails, the latest version of GGTS (3.6.4) did not work properly with the latest version of Grails (3.0.1). Fortunately the GGTS bundle came with an older version of Grails (2.4.4), and by referencing that, GGTS would work correctly. However, although I changed the IDE reference to Grails, I forgot to reset my environment variable ...
So GGTS was setting up the project for using Grails 2.4.4. However, when calling grails war, the command was using Grails 3.0.1! Apparently these two versions of Grails use different files for creating a WAR file, so GGTS was not setting up the project directories with the correct local files, and the packaging was failing.
Avoiding Future Occurrences
So, when using GGTS 3.6.4, make sure that all references to Grails point to Grails 2.4.4.
In general, if any GGTS bundle contains a version of Grails, you should have everything set up to use that version, even if it is old.
this plugin requires plugin Editor Library to be installed.
The plugin Editor Library is requested in version >= 2.10.1.10.2 (release version 2) but only 3.46.1.22.43 (of release version different from 2) was found.
The following plugin is affected: Struts2 Support
Now i have resolved another plugin for Struts 2 support. This plugin is called Netbeans Struts2 Plug-in and its a re-pack for the plugin i was trying to install. Though this plugin in not certified but it is working good. The developers have tested it on netbeans 7.4 but i'm using it not netbeans8 and i have not suffered any issues.
I have found another way, that is using maven. That is also a good way but i would not recommend it if you have slow internet connection.
I am struggling to configure grails 2.3.X in IntelliJ idea 12.0.1. Grails 2.2.X is configured successfully.
Grails 2.3.2 is working properly from terminal. I can compile, test, run my application. But while trying to configure it in IntelliJ so that dependencies get resolved, I get the IntelliJ shouting straight to me(as pictured below).
Looks like Grails Distribution in specified path is broken. Cannot
determinate version.
What I see is changes in grails-2.3.x/dist/ to earlier version's grails-2.2.x/dist/.
Is this because there's no support for newer version(2.3.x) of grails in IntelliJ 12 or what ?
I want nothing else but my application (jar) dependencies to be resolved in the IDE.
Make sure you are running the latest version of IntelliJ IDEA - v12.1.6. There was a "Grails 2.3.0 not working" bug fixed in 12.1.6.
You may also want to take a look at the Grails SDK is not configured question. One of the IntelliJ IDEA developers has a detailed answer in that question that may help.
Also, this thread on the IntelliJ IDEA forum may be useful.
For Information to reload the dependencies in IntelliJ 12.1.6 , following path works fine.
Tools
-> Grails
-> Synchronize Grails settings
I thought I'd give Grails and IntelliJ a look. However, I'm struggling at the first hurdle.
When I go to select the "Groovy SDK" I'm choosing my installation directory - in this case, Grails 2.2.0 - but the OK button on the IDE stays grayed-out. If I choose another of my installation directories - Grails 1.3.7 - the OK button is activated but I get an error message saying my groovy installation is broken.
Does anyone know what I'm missing?
I'm using IntelliJ 12 Community Edition and trying to use Grails 2.2.0.
Thanks.
Please checkout this IntelliJ IDEA Features page, and you will see that some web technologies, like Grails, are only supported in the Ultimate Edition. I would recommend upgrading to the Ultimate Edition, since it has excellent Grails support.
As an alternative, use can use a free IDE which has Grails support: STS, GGTS.
Community Edition doesn't support Grails development. Note that it is asking for a Groovy SDK (which is supported), not a Grails SDK.
I am using NetBeans 7.1, which comes with Groovy 1.6 support. I have to do a Grails project, but with Groovy 1.8 support. So I downloaded Groovy 1.8 installer, installed it and added the Library in Netbeans -> Tools -> Libraries (and removed Groovy 1.6 library).
Now whenever I use some stuff added in Groovy 1.8 within my Grils project, it still underlines it and throws "cannot resolve" error... I was googling it for last 2 hours and everything I find seems I have already done... it starts to give me a headache... Any suggestions on how to solve it?
NetBeans support from Groovy has -- until recently -- stagnated.
The Groovy support (as you say) is for Groovy 1.6.X, and the Grails support is similarly old.
There has very recently been some activity in trying to improve this, but at the current time you are probably better using Eclipse, STS (both free) or IDEA (paid) if you want proper IDE support for up to date Grails development.