A new version of eclim is now available with support for Eclipse 4.6 (Neon).
A new version of eclim is now available with support for Eclipse 4.5 (Mars).
The latest version of eclim is now available with scala support re-enabled, new groovy support, java debugging support, many bug fixes, and more.
Eclim has finally been released with Eclipse Luna support. Please note however that scala support is disabled in this release. I tried waiting for a final release of ScalaIDE 4.0.0 for Luna, but I don’t want to hold up the rest of eclim any longer. If you want to use eclim’s scala support, you’ll need to install the ScalaIDE 4.0.0 milestone and build eclim from the master git branch.
Eclim has been updated to fix an issue on Windows that could prevent many features from working.
This release includes many bug fixes and refinements as well as a rewrite of eclim’s python support to utilize pydev instead of rope.
Warning
Any exiting eclim python projects you have should be re-created with the new
python nature:
:ProjectCreate /path/to/project -n python
This release fixes the extraction of the necessary vim files when installing scala support.
The previous eclim installer for Kepler was still pointing at the Juno update site. This release remedies that.
The focus of this release is to bring eclim fully up to date with Eclipse Kepler support. The installer for eclim 2.3.0 now requires that you install against Kepler.
This is primarily a bug fix release with a few new features. Unless some critical error is found, this will be the last release targeting Juno. The next release will likely target Kepler though this release should work fine on Kepler as well, with the exception of scala support which has not been tested. Indigo support will continue but will likely end with the release of Luna, possibly sooner.
Eclim has been updated to support the Android Development Toolkit version 22.0.0, scala is now supported for both Juno and Indigo, and there are a few other improvements and many bug fixes.
The most notable change in this release is support for Eclipse 3.8 with the Indigo release (1.7.13). Both releases also include several small bug fixes.
This is another bug fix release which includes support for the latest Android development toolkit (21.0.0).
This is a bug fix release for Windows users which fixes executing of eclim commands from vim:
Two new eclim updates are once again available with several bug fixes and improvements.
Please note that the Scala IDE , which eclim uses to provide scala support, is not yet available for Eclipse 4.2 (Juno), so eclim’s scala support will not be available for the eclim 2.2.x releases until sometime after the Scala IDE has been updated for Juno.
Another set of releases are now available for both Juno and Indigo. These both include several bug fixes along with new support for creating android projects.
Eclim also has a newly redesigned site using the sphinx bootstrap theme.
Two new versions of eclim have been released, one for the latest Eclipse version, Juno, the other a bug fix release for the previous version of Eclipse, Indigo.
Warning
Non vim users (emacs-eclim, subclim, etc.): The underlying command response format for eclim has changed, which means that any project relying on the old format isn’t going to work. So if you are installing eclim for use with a client other than vim, then be sure to check with the client project to see if it has been updated for eclim 1.7.3 or later.
I’d also like to announce the #eclim channel on freenode.
Eclim has been upgraded to support Eclipse 3.7 (Indigo).
Note
Eclim now requires Eclipse 3.7.
Eclim has been upgraded to support Eclipse 3.6 (Helios).
Note
Eclim now requires Eclipse 3.6.
Eclim has been upgraded to support Eclipse 3.5 (Galileo).
Note
Eclim now requires Eclipse 3.5.
Ruby support has been added using the eclipse dltk.
Also note that the eclipse pdt plugin which serves as the base for eclim’s php support has not yet been released for the latest version of eclipse. For this reason php support has been temporarily removed from this release and will hopefully return soon after the pdt team release a Ganymede (3.4) compatible version.
Another major change worth noting, is that eclim is now licensed under the GPLv3. This was done to give eclim the freedom to integrate with other GPL projects in the future.
Eclim has been upgraded to support Eclipse 3.3.
Note
Eclim now requires Eclipse 3.3 and JDK 1.5.
A new graphical installer built on the formic installer framework.
New functionality based on and requiring the eclipse wst.
Many more changes.
All Users: A bug made its way into the initial 1.2.3 release which prevents you from adding methods via :JavaImpl.
An updated eclim_vim_1.2.3.jar is now available to resolve this issue. If you downloaded this file on October 8th or 9th you can either download the updated version or execute the following within vim:
:PatchEclim eclim/autoload/eclim/util.vim 1.27
Please view the release notes for more info.
To see a list of fixes you may view the release notes.
To see a list of what’s new / changed, be sure to take a look at the release notes.
Windows Users: Eclim 1.2.0 contained a couple issues that can potentially prevent eclim from functioning. A new version of eclim_vim_1.2.0.jar is now available, which fixes these issues.
Simply download the new file and extract it as explained in the <a href=”guides/install.html#step3”>installation guide</a>. There is no need to download or re-install the Eclipse plugins.
If any other issues are encountered please report them.
To see a list of what’s new / changed, be sure to take a look at the release notes.
Warning
The layout of eclim plugins within the Vim runtimepath has changed. Please read the <a href=”changes.html#upgrade_1.2.0”>details</a> in the release notes and take the appropriate action prior to upgrading.
To see a list of what’s new / changed, be sure to take a look at the release notes.
To see a list of what’s new / changed, be sure to take a look at the release notes.
To see a list of what’s new / changed, be sure to take a look at the release notes.
The first eclim release (1.0.0) is now available. All questions, issues, suggestions are welcome and encouraged.
Be sure to read the docs to see what features are currently available, and take a look at the <a href=”todo.html”>todo</a> to see what’s coming in future releases.
Several new additions over the past couple weeks:
With the addition of these features I’m going to stop adding new functionality for the time being and focus on testing and ensuring that everything works as expected on Windows.
Code navigation / searching is done! Most of the Vim integration for searching is done as well. The only thing missing is viewing code for results that are found in a jar file that have no corresponding source attachment. I may end up doing what Eclipse appears to do, which is to use javap to display the class and method signatures. That or I’ll use jad to decompile the whole source. My only issue with jad, is that it is not up to date with the 1.5 byte code.
I also have automated importing done as well. The eclim server request just returns a list of possible results to import for a given request and the editor (Vim in this case) handles prompting the user and updating the code.
Note
The Vim integration now requires Vim 7. Even though Vim 7 is still alpha, I haven’t had any major issues with it and the new additions to the Vim scripting language are just too good to pass up.
My next step is to start documenting everything and testing on a Windows environment to ensure there aren’t any compatibility issues.
After that I should be ready to put out a preliminary release. I’m trying to be very careful about releasing anything too soon. The last thing I want it to scare anyone off with a broken project that doesn’t seem to work properly.
Sourceforge site is up! Now it’s just a matter of getting the ball rolling again.
I’m hoping to have source code navigation working by the end of next week. This includes the ability to simply hit <enter> on a class name, method name, method call, etc. to jump to its declaration. Basically I want to replace my previous Vim plug-in with the new Eclipse one.
Before I put out any releases though, I want to have a comprehensive set of documentation. For the first few releases, setup will probably be pretty manual, with most of it occurring through the Eclipse interface. Going forward, I want to move more of that functionality into Vim.