Hello Dave,

thats sounds good. But I would propose:

- org.codehaus.groovy.runtime.libraries
- org.codehaus.groovy.runtime.source

This could be part of a target platform we could use later to simplify
development and automatically builds.

Thorsten

Dave Dunkin schrieb:
> I'd like to propose that the org.codehaus.groovy plugin be split into a
> runtime plugin and a development plugin. The main reason is to trim down
> the size of the plugin required for running groovy code. I have an RCP
> application that uses groovy. If I include the org.codehaus.groovy
> plugin, that's 12MB because it includes all the classes twice (once in
> groovy-all-*.jar and once in the separate jars for groovy and its
> dependencies) and the source.
>
> I suggest moving antlr-2.76.jar, asm-2.2.jar, asm-tree-2.2.jar and
> groovy-1.5.1.jar to org.codehaus.groovy.eclipse.core. I think
> commons-cli-1.0.jar could be removed altogether. The source files can be
> moved to generated source plugins. This will leave the runtime
> org.codehaus.groovy plugin lean and mean for use in RCP applications.
>
> I have these changes made in my local workspace and am currently testing
> them. Everything seems to be working well.
>
>  


--
Thorsten Kamann
Software-Architect, Consultant, Coaching
Germany, NRW

thorsten.kamann@(protected)
http://www.thorsten-kamann.de/
callto://thorque

Fornax-Platform - Platform for developing MDSD-related Tools and components
http://www.fornax-platform.org/


---------------------------------------------------------------------
To unsubscribe from this list please visit:

  http://xircles.codehaus.org/manage_email