On Mon, Jan 10, 2011 at 14:00, Adam Murdoch <[email protected]> wrote: > Hi, > At the moment the 'eclipse' and 'idea' plugins attempt to merge the > project's dependencies (as defined in the build script) with the existing > IDE classpath defined in the .classpath/.iml file. > However, the implementation doesn't really work, so that you end up with old > dependencies in the IDE classpath as your project dependencies change over > time. > While it is possible to fix this, it doesn't, to me, seem worth the effort. > Instead, I'd like to remove the merging. After this change, the 'ideaModule' > or 'eclipseClasspath' tasks will ignore the existing classpath and replace > it with the dependencies defined in the build script. The result will be a > much more accurate IDE classpath, at the cost of losing any manual > configuration you might have made to that classpath. > Note that I'm talking about the classpath only - the merging of other > configuration in the ide files will continue to work. > > Anyone have a good reason to keep (and fix) the dependency merging? > > -- > Adam Murdoch > Gradle Developer > http://www.gradle.org > CTO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz > >
Only what you mentioned Adam. However, I really don't see this being too big of a problem. I don't foresee many people adding deps manually then regenerating the project from gradle again. -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
