On Wed, Jan 20, 2010 at 12:16 PM, Steven Devijver <[email protected]>wrote:
> > > > Thanks for your answers.... they really do help :-) > > I know of ant4eclipse and we currently using it... but actually I do want > to > be free of that. > > The conversion I would need is: > > - find out the project dependencies via .classpath file > - resolve them to the local repository > > ant4eclipse cant do that - but if its that easy as Hans wrote... that would > be great > > Cheers > Marty > > === > > The entire ant4eclipse setup could be abstracted through a method like > getDependenciesFromEclipse(). If ant4eclipse does the job of reading > .classpath files well without getting in the way - something which should be > determined - its classes should be reused by Gradle, maybe by abstracting > the entire thing in a plugin. > That would be a very nice plugin considering the realities of many projects. >From a build point of view the downside of using Eclipse metadata as master is that this metadata is lacking richness. Most importantly they don't have scopes (IntelliJ 9 has scopes now). - Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleorg CEO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz Steven > >
