• Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0, 1.1-rc-3
    • Fix Version/s: 1.6-rc-1, 1.6-rc-2, 1.7.0
    • Component/s: None
    • Labels:
    • Environment:


      Now that Java 6 released, there's a lot of interest going around about the new JSR 223 scripting platform. Unfortunately, neither Java SE 6 nor the current Groovy builds support JSR 223-style Groovy out of the box.

      Fortunately, adding this to Groovy is trivial. The code is both simple and available from the JSR 223 reference implementation ( The license permits redistributing as source or binary as long as mention that some code comes from Sun and release them from liability.

      Ideally, the Groovy project should integrate the three implementation classes and the service declaration into groovy-1.0.jar. If you do this, simply dropping Groovy into your classpath is enough to enable the Groovy engine. At the very least, we should bundle the RI's groovy-engine.jar into the groovy binary distribution. Finding and installing the Sun RI is a bit of a pain and will discourage would-be users.

      Behind the scenes, scripting engines get enabled by adding a file to the META-INF/services directory of a JAR as specified in the new Java 6 java.util.ServiceLoader ( This file just tells the JVM that it can find a service implementation in a specific class. For JSR 223, the implementation is just a concrete ScriptEngineFactory and a couple of support classes:

      I'm happy to volunteer any assistance that might help make this part of the Groovy distribution. However, adding these classes and the service definition to groovy-1.0.jar should be trivial and will provide a great service (pun intended).




            • Assignee:
              jimwhite James P. White
              gerweck Sarah Gerweck
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: