Groovy Classpath Container should be a system classpath entry, not an application

From the mailing list:

===================
Hi,
I`ve noticed that the Groovy Libraries in Milestone 1 release are being added to the "User entries" on the classpath.
Is this necessary? I ask as the easyb plugin when launching uses whats in the "user entries" to launch the easyb runner.

This is picking up the groovy libraries but we`d like to be able to specify a different groovy library if possible.

We build the classpath by using AbstractJavaLaunchConfigurationDelegate.getClasspath(ILaunchConfiguration configuration)

This filters out the Bootstrap entries so it would be good if we could filter out the groovy library as well.
Other plugins which use the launch delegate may also be effected if they rely on groovy.

===============

Next message:

===============

After looking at the Groovy plugin code can the

GroovyClasspathContainer.getKind()

Be changed from

public int getKind()

To

public int getKind() {
return K_SYSTEM;
}

I believe this would make the classpath entry a bootstrap entry. The Groovy libs are more of a system library then an application library any way.

I think this would stop the Groovy jars being included in the user classpath.
Or would this break the plugin?