Thanks Peter. The hooks from the guide turned out to be the ticket. Haven't done the full thing yet but seems very promising.
- Peace Dave On Tue, Feb 22, 2011 at 11:31 AM, Peter Niederwieser <[email protected]> wrote: > > > Dave King wrote: >> >> Any ideas on how we could provide a property or properties that would >> tell the eclipse task to generate project dependencies instead of jar >> dependencies? >> > > You could try to achieve this by manipulating > EclipseProject.referencedProjects and EclipseClasspath.minusConfigurations. > For WTP projects you'd also have to reconfigure the EclipseWtp task (which, > by the way, has been split into two for the upcoming 1.0-milestone-1). Other > options: > > 1. Use "git submodule" to create an aggregate Git project and aggregate > Gradle build. This is what the Qi4j project does (see > https://github.com/Qi4j/qi4j-sdk). > 2. Post-process the Eclipse files generated by Gradle according to your > needs. The user guide explains how to do this. > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Creator, Spock Framework > http://spockframework.org > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Switch-between-jar-and-project-dependency-for-eclipse-tp3395869p3395954.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
