Jump to: navigation, search

Difference between revisions of "Add the ability to write plugins using jruby or groovy."

Line 1: Line 1:
This project is part of [http://wiki.eclipse.org/index.php/Google_Summer_of_Code_2007 Google Summer of Code 2007]
This project is part of [http://wiki.eclipse.org/index.php/Google_Summer_of_Code_2007 Google Summer of Code 2007], project link is [http://code.google.com/soc/eclipse/app.html?csaid=OR0QXQpDWygVNwUkFAZQWi1LOxwJSVNQUCJVaUFdSQ0HAXUEPUEA%0A here].
Student: Anton Arhipov  
Student: Anton Arhipov  

Revision as of 13:45, 4 June 2007

This project is part of Google Summer of Code 2007, project link is here.

Student: Anton Arhipov

Blog: http://arhipov.blogspot.com


Scripting language like Groovy (or JRuby) is an ideal choice for Java developer to do quick prototyping. The biggest benefit of Eclipse support for Groovy plug-in development is that while changing the plug-in on-the-fly there's no need to start a separate Eclipse instance or restart the IDE when something was changed in the code. This would rapidly improve the speed of lightweight plug-in development.

This project aims to add ability to write plugins in JVM-based scripting language, like Groovy and JRuby. But it could be a starting point for any other JVM scripting language, like BeanShell or Jython.


The main results to be reached:

- An Eclipse extension/plug-in to (re)load (Groovy/JRuby) scripts on the fly.

- Command line console support to modify and change the program behavior interactively. This could look like in case Apache Derby ij plug-in