Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Add the ability to write plugins using jruby or groovy."
(→Deliverables) |
(→About) |
||
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] | ||
+ | |||
+ | Student: Anton Arhipov | ||
+ | |||
+ | Blog: [http://arhipov.blogspot.com/search/label/soc http://arhipov.blogspot.com] | ||
+ | |||
== About == | == About == | ||
Revision as of 12:04, 16 April 2007
This project is part of Google Summer of Code 2007
Student: Anton Arhipov
Blog: http://arhipov.blogspot.com
About
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.
Deliverables
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