The SpringSource Tools Team is proud to release Groovy-Eclipse 2.5.0. In this release, we are most proud of our new DSL Descriptors (DSLDs) feature, which provides scriptable support for custom Domain Specific Languages in the Groovy Editor. Additionally, this release includes Groovy 1.8 as an optional add on, better content assist and type inferencing, and a Groovier outline view.
See all details on the New and Noteworthy page, and please send your comments to the mailing list. Enjoy!
Thursday, May 12, 2011
Monday, May 9, 2011
Better DSL Support for Groovy-Eclipse
What have I been doing lately? Mostly working on Groovy-Eclipse's new DSLD feature to support custom Groovy DSLs more easily. See my post about that on the SpringSource blog.
Friday, April 8, 2011
Next month at the GR8 conference
The nice folks organizing the GR8 Conference 2011 Europe have posted an interview they did with me. You can read it here. The GR8 conference focusses on the Groovy eco-system including Grails, Gradle, and Griffon.
I'll be talking about Groovy-Eclipse, Grails tooling, and our new Gradle support for Eclipse. More on this soon...
I'll be talking about Groovy-Eclipse, Grails tooling, and our new Gradle support for Eclipse. More on this soon...
Friday, March 18, 2011
Groovy-Eclipse and AJDT simultaneous releases
Today, we have just release Groovy-Eclipse 2.1.2 and AJDT 2.1.2. By coincidence, they both have the same version number.
We've made lots of improvements to Groovy-Eclipse including inline renaming support, mark/find occurrences as you type, and type inferencing improvements. You can find all the details at the New and Noteworthy page.
The update site for installation on Eclipse 3.6 is here:
http://dist.springsource.org/milestone/GRECLIPSE/e3.6/
We are also now releasing a Groovy-Eclipse for Eclipse 3.7 (Indigo). The update site is here:
http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/
As always, please raise bug reports and enhancement requests at our Codehaus issue tracker.
We expect to release Groovy 1.8 support shortly.
Our enhancements for AJDT have mostly centered around supporting Intertype Inner Types. a new AspectJ language feature. You can read about it at the AJDT New and Noteworthy.
An AJDT release for Eclipse 3.7 is available at this update site:
download.eclipse.org/tools/ajdt/37/dev/update/
Please raise bugs and feature requests at Eclipse's bugzilla.
Groovy-Eclipse
We've made lots of improvements to Groovy-Eclipse including inline renaming support, mark/find occurrences as you type, and type inferencing improvements. You can find all the details at the New and Noteworthy page.
The update site for installation on Eclipse 3.6 is here:
http://dist.springsource.org/milestone/GRECLIPSE/e3.6/
We are also now releasing a Groovy-Eclipse for Eclipse 3.7 (Indigo). The update site is here:
http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/
As always, please raise bug reports and enhancement requests at our Codehaus issue tracker.
We expect to release Groovy 1.8 support shortly.
AJDT
Our enhancements for AJDT have mostly centered around supporting Intertype Inner Types. a new AspectJ language feature. You can read about it at the AJDT New and Noteworthy.
An AJDT release for Eclipse 3.7 is available at this update site:
download.eclipse.org/tools/ajdt/37/dev/update/
Please raise bugs and feature requests at Eclipse's bugzilla.
Monday, March 7, 2011
eGit in practice
I like Git in theory. Distributed version control has many advantages over non-distributed including local branching, easier task switching, and easier offline work. However, as an Eclipse user, I find it highly disruptive to drop down to the command line whenever I need to perform any git commands. Despite its advantages, using git instead of CVS or SVN has felt like a big step backward because of its lack of Eclipse tooling.
Until now, I have only been using git occasionally, and so I could live with the inconvenience. However, it looks like some of my major projects will be moving to git and so I need to figure out what to do. I have been eagerly awaiting the eGit tooling to reach a reasonable level of maturity. I decided to try it out and see how far along it is.
I installed eGit 0.11.3 from the public repository (http://download.eclipse.org/egit/updates) into my SpringSource Tool Suite. And as expected, the Git Repository perspective was initially empty. So far so good.
I thought I'd start by cloning the SpringIDE project. Initially, I tried right clicking in the Git repositories view, and expected that I'd be able to pasted the repository URL directly. That didn't work. There is only one option: to paste an existing repository path:
Instead, I used the "clone repositories" command button. I was able to do what I wanted to, but it was slightly less intuitive than I would have hoped.
After cloning, Git placed the entire repository on my hard drive, which is nice because checking out, exploring, and comparing is much faster than using a traditional VCS. Performing these operations within Eclipse is just as speedy as doing things like comparing local history. At this point, I was very impressed.
Then I made a single change to a file and things started going downhill. After the change, I had to wait about 30 seconds for the '>' to appear in the package explorer next to the changed file (whereas with Subversive and the CVS tooling, this happens what seems like instantaneously):
Then I started playing around... I right-clicked on the file I had just changed and selected Assume unchanged. Uh-oh! ClassCastException. Now, click Assume changed. IOException. Apparently, though something worked and I was able to continue with the commit and then view the commit in history.
Next problem: I moved back to the Git Repositories perspective, and I had lost all of the git repositories in the git repositories view. Re-importing them would not work. It looked more like the UI had crashed than any data had been lost:
I restarted Eclipse and everything seemed back to normal:
Despite its problems, eGit has a good UI. The project is clearly following the Eclipse User Interface Guidelines, and I was able to easily transfer my familiarity with Eclipse's CVS and SVN tools to working with git. This is a strong indicator to me that the project is headed in the right direction even if it is not quite there yet.
The basic features that I need exist, but after 20 minutes of using, I hit several obstacles. None of them were insurmountable and the project is usable. Despite this, I do expect that future releases will be significantly more solid. I will likely be using eGit for my day to day work, but for now this will be largely for repository and history exploration, rather than for commit and branch management, which I'll probably use the command line for.
EDIT: I raised Bug 339158 and Bug 339159 to track some of the problems I found.
Until now, I have only been using git occasionally, and so I could live with the inconvenience. However, it looks like some of my major projects will be moving to git and so I need to figure out what to do. I have been eagerly awaiting the eGit tooling to reach a reasonable level of maturity. I decided to try it out and see how far along it is.
Install and setup
I installed eGit 0.11.3 from the public repository (http://download.eclipse.org/egit/updates) into my SpringSource Tool Suite. And as expected, the Git Repository perspective was initially empty. So far so good.
I thought I'd start by cloning the SpringIDE project. Initially, I tried right clicking in the Git repositories view, and expected that I'd be able to pasted the repository URL directly. That didn't work. There is only one option: to paste an existing repository path:
Instead, I used the "clone repositories" command button. I was able to do what I wanted to, but it was slightly less intuitive than I would have hoped.
Using eGit
After cloning, Git placed the entire repository on my hard drive, which is nice because checking out, exploring, and comparing is much faster than using a traditional VCS. Performing these operations within Eclipse is just as speedy as doing things like comparing local history. At this point, I was very impressed.
Then I made a single change to a file and things started going downhill. After the change, I had to wait about 30 seconds for the '>' to appear in the package explorer next to the changed file (whereas with Subversive and the CVS tooling, this happens what seems like instantaneously):
Then I started playing around... I right-clicked on the file I had just changed and selected Assume unchanged. Uh-oh! ClassCastException. Now, click Assume changed. IOException. Apparently, though something worked and I was able to continue with the commit and then view the commit in history.
Next problem: I moved back to the Git Repositories perspective, and I had lost all of the git repositories in the git repositories view. Re-importing them would not work. It looked more like the UI had crashed than any data had been lost:
I restarted Eclipse and everything seemed back to normal:
Despite its problems, eGit has a good UI. The project is clearly following the Eclipse User Interface Guidelines, and I was able to easily transfer my familiarity with Eclipse's CVS and SVN tools to working with git. This is a strong indicator to me that the project is headed in the right direction even if it is not quite there yet.
And so...
The basic features that I need exist, but after 20 minutes of using, I hit several obstacles. None of them were insurmountable and the project is usable. Despite this, I do expect that future releases will be significantly more solid. I will likely be using eGit for my day to day work, but for now this will be largely for repository and history exploration, rather than for commit and branch management, which I'll probably use the command line for.
EDIT: I raised Bug 339158 and Bug 339159 to track some of the problems I found.
Friday, October 22, 2010
AJDT 2.1.1 Released
I am pleased to announce the release of AJDT 2.1.1. In this release, we have focussed on AspectJ-aware searching and refactoring. This release also includes AspectJ 1.6.10.
Please see the New & Noteworthy for more details, including a list of refactorings that are currently known to work in AspectJ files.
AJDT 2.1.1 will be available in the upcoming SpringSource Tool Suite 2.5.0 release, or you can install it from one of the following update sites:
Eclipse 3.6: http://download.eclipse.org/tools/ajdt/36/update
Eclipse 3.5: http://download.eclipse.org/tools/ajdt/35/update
Please see the New & Noteworthy for more details, including a list of refactorings that are currently known to work in AspectJ files.
AJDT 2.1.1 will be available in the upcoming SpringSource Tool Suite 2.5.0 release, or you can install it from one of the following update sites:
Eclipse 3.6: http://download.eclipse.org/tools/ajdt/36/update
Eclipse 3.5: http://download.eclipse.org/tools/ajdt/35/update
Thursday, October 7, 2010
More on Groovy-Eclipse and Maven
I've had a few requests for the source code for the Groovy-Eclipse integration for maven, as well as a sample project that uses it. You can get both the sample project and groovy-eclipse compiler plugin for maven.
They are packaged as two m2eclipse projects, and it is recommended (although not necessary) to import them into Eclipse to use them.
The
The
Please let me know if you have any problems.
They are packaged as two m2eclipse projects, and it is recommended (although not necessary) to import them into Eclipse to use them.
The
groovy-eclipse-compiler project contains the compiler integration. It is a single Java class that calls into the Groovy-enhanced JDT compiler. This maven plugin uses plexus to hook into maven's compiler plugin.The
groovy-eclipse-maven-tests project is a very simple maven project that has a few Groovy and Java classes that interact with each other. If you want to create your own project using the Groovy-Eclipse maven integration, I would recommend starting with this sample project.Please let me know if you have any problems.
Subscribe to:
Posts (Atom)