Has anyone been successful in getting the grails plugin for eclipse to work? How about grails plugin with netbeans?
If you use the NetBeans 6.5 Beta you'll see the Grails functionality is promising, but still buggy(minor). The good thing is in 6.5 Groovy and Grails support is standard, you don't have to install the plugins.
Unfortunately, there hasn't been much progress on the Eclipse plugin for Grails, we have started using IntelliJ IDEA for Grails development, the JetGroovy plugin is excellent and keeps getting better!
Netbeans 6.5 is pretty good for Grails and allows for debugging, though the code completion is just barely there.
Well, here's a quick update. The Eclipse plugin works, and has refactoring support. But, for some reason I can't get it to recognize the Grails plugins in the Eclipse project.
It's starting to come along though.
I haven't had any problems getting the Eclipse grails plugin "to work" insofar as it's installed and providing all the features advertised. The problem is that this set of features is minimal, and light years behind IntelliJ. I understand that switching from a free IDE to a commercial IDE isn't at all possible, but if it is, do it! Although Netbeans is better than Eclipse, it's still quite a distance behind IntelliJ.
Just for future documentation:
Netbeans 6.8 is available with a very nice Grails/Groovy Plugin that works like a charme.
Additionally you can use a new Code Coverage Plugin.
Really nice build.
Link:
Netbeans Homepage
But you have to keep in mind that Grails now belongs to Spring Source. Spring Source is known for developing their own Tool Suite based on Eclipse. Maybe we will see a better grails plugin implementation for Eclipse.
Related
We are experimenting with Grails development on Eclipse STS, and one of the most annoying problems is that, unlike Java code, there does not appear to be any code insight features for Grails and Groovy classes and methods. Only after compiling and running a Grails web app do we find out that a method or field name does not exist.
Seriously, there has to be something out there for minimal code insight (hoping).
I am sure that STS can in fact do this for you, it is basically what its Grails support is all about. Are you sure you have installed the right plugins? Documentation on this subject is right here: [1]: http://www.grails.org/STS+Integration
Side note: while STS does a decent job, I have been a happy user of IntelliJ IDEA Ultimate edition and have never looked back to eclipse once i switched :)
I have a service - reportservice.groovy which has a big list of imports, many of them unused. Is there a quick way in Netbeans IDE 7.0 to remove the unwanted ones. (its not showing any warning/error stripes in the right column). If some plugin does this check I would like to know it.
Thanks
Priyank
Netbeans support for both grails and groovy is about 2 years old.
if you want an ide, you're better off using Eclipse with the latest groovy plugin installed, or sts from Spring
or intellij paid edition has great support as well
what is the best goovy plugin for eclipse (helios)? I have download Groovy-Eclipse but the plug-in seems not good? cant go to methods by clicking ctrl and also cant debug too
The best Eclipse Groovy/Grails support is provided by the STS Eclipse distribution. If you're not using Grails and are only interested in Groovy I don't think you'll find this much better than the Groovy-Eclipse plugin, because I expect STS itself uses the Groovy-Eclipse plugin.
The best Groovy/Grails support is provided by IntelliJ. Eclipse has always been a long way behind.
Unfortunately, groovy-eclipse is the best there is.
If you want to improve your experience, I can only recommend switching to IntelliJ IDEA.
Groovy-Eclipse is your only option for editing groovy code in Eclipse.
Since the behavior you describe that is missing is a fundamental part of Groovy-Eclipse (ie- navigation to method declarations), it sounds like something is not set-up properly in your project. Perhaps your groovy sources are not on the Eclipse build path of your project. Make sure this is the case and let me know if this fixes your problem.
Since SpringSource / VMWare embraced the Grails and Groovy community, SpringSource Toolsuite (STS) has really increased the quality and integration of Groovy into the Eclipse environment. If you haven't looked at it recently, STS 2.7.0 was just released, and it includes support for Gradle, Groovy 1.8, and initial support for Grails 1.4 / 2.0. Groovy-Eclipse is the bundled Groovy solution, and enables the Groovy compiler, Groovy project types, as well as a number of other areas.
It's also important to note that the development is going at a pretty good place - some of the standard editing features are fixed month to month as dot releases are released often.
Intellij is also continuing to provide a great solution - but now that the Eclipse support is improving, there are two viable choices for developers to look at.
STS is available for Eclipse 3.6 and 3.7.
I understand that SpringSource Tool Suite is based on Eclipse.
I am coding Grails. STS is often pissing me off. I was thinking of installing Eclipse instead with a Grails plugin - will it just be the same?
What's better? STS or Eclipse?
Have you considered IntelliJ, it has excellent Grails and Groovy support. I had been a eclipse guy for years but I am loving IntelliJ now.
IntelliJ Grails Features
I believe STS incorporated the original Groovy plugin so you're honestly better off with STS than you are trying to hack together Eclipse with the old plugin.
That said, other IDEs with good Groovy/Grails support are:
IntelliJ IDEA: http://www.jetbrains.com/idea/features/groovy_grails.html
NetBeans: http://netbeans.org/features/groovy/ (but development on Grails support appears to have stopped since 6.8.0)
I've personally tried IntelliJ and I liked it for Grails. I have not tried NetBeans but I've heard it is good.
STS has better Groovy n Grails support. The latest version i.e. 2.5.0 has better features and bug fixes. I would suggest you stick to STS rather than Eclipse. I have been using it for last couple of months and it is very stable. The latest version has much better features and is more stable than previous versions.
I found Eclipse with the Grails plugin easier to configure than STS, so I started out down that route. STS seems overly clunky and too specialized - if your app is anything over than a very vanilla grails app I'd say Eclipse is better.
Having said all of that, I tried IntelliJ IDEA and fell in love with it. I even forked out the $200 for a personal licence when my company said no to buying a license!
STS is an Eclipse distribution packaged by SpringSource, who also own Grails project. You should bring your specific issue to the vendor or at least describe them in your question.
I think you should definitely opt for STS - the integration of the Groovy resp. the Grails plugin is much better than in Eclipse.
On the other hand, the question is hard to answer without getting religious subjective; what are the issues you encoutered in STS and what makes you think they won't occur or even be more annoying in the main Eclipse distribution with no native Groovy/Grails support?
I have been unsuccessful trying to use the Grails plugin on Eclipse. After a lot of work finding the right repositories for missing dependencies, the Grails plugin practically took over Eclipse, it became a quasi STS Eclipse. Even the home window became the STS window!
I guess the producers of STS are basically trying to convince you to switch to STS, instead of using their almost worthless plugin, and going through the pain of getting the plugin working, and getting at the end a STS clone.
You are better off just using STS, but it angers me that people who like Eclipse or MyEclipse have to be forced to use STS' specific version of Eclipse.
I've downloaded and started to use Drools on a pilot project via it's "default" platform Eclipse. However, I would like to use it in Netbeans just the way plug-in works in Eclipse.
Any ideas/shot-cuts to do that?
There are quite a lot of features in the eclipse plugin, but there is (as yet) no plugin for eclipse.
You can of course use drools with netbeans just fine - just means that the IDE features that are rule specific won't be available, but it will work, its Just Another Library then !
(I use drools with intelliJ IDEA and I just created a little syntax definition to give me basic highlighting etc... but no other features. If I want them, I jump into eclipse).