In your patch you always set the "EXPORTED" attribute true. I'm not sure if this is good practice. In my custom builds I added some methods to a extended eclipse plugin to support the following syntax:

....
defaultExport = false

dependencies {
compile("commons-logging:commons-logging:1.1"){
export

}
}
...

What do you think about this syntax? I would like to have something like this:

dependencies {
compile("commons-logging:commons-logging:1.1")

}

but I failed to support this syntax by just adding code to the plugin and without changing the dependencyhandler.

any thoughts? I would like to share my additions to the eclipse plugin if desired.

regards,
René

@Rene It is now possible to add a syntax like the one you would like. For a little snippet on how you could make use of that in the Eclipse plugin, see: http://pastebin.com/8kP2FiFq

Hi there, I've added basic support for the export feature at http://github.com/breskeby/gradle/tree/GRADLE-644 will add some documentation and maybe some more tests before sending a pull request. bye bye

@Rene Excellent

Hi there, I've just send a pull request to you with a patch. I added some stuff to the userguide too. I'm not that happy with the implementation I used to allow configuration wide export configuration in the EclipseClasspath. I would like check for exporting before calling "addDependsOnProjects()" and "addLibs()" from createXmlDocument(). But somehow that doesn't work because of some groovy foo on getClasspathLibs(). the patch is hosted at http://github.com/breskeby/gradle/tree/GRADLE-644
regards,
René

I appears the additions to the userguide and the samples (eclipse-export-usage and eclipse-export-bulk) did not make it into trunk. Can they be added as well, otherwise it is hard to know how to use this.

thanks,
Philip

This will come soon.

There is now an updated version of the user's guide. Fine grained settings regarding the export can be done via they whenConfigured hook.