Our future plans are very different.
Interesting; apologies if I’m making you rehash something that’s on a published roadmap, but you’ve piqued my interest…what are your future plans that are so different?
If you’re planning on making your dependency code more independent of gradle (which is great), won’t you essentially be making an ivy competitor/replacement?
(This would be just with me…I use a variety of build tools, haven’t had a chance to use gradle yet, but I think Ivy made a strong case that having a “only dependencies” file, separate from the build file, was a nice way to go, as then your IDE (e.g. IvyDE) could pull in the ivy.xml and not have to know whether you were using buildr or gradle or sbt or ant or whatever. Given how much of a pita Eclipse plugins are, it makes sense to write that just once, I think.)
(Generating .classpath files is a great start, but then you can’t “resolve references in workspace” which is, IMO, a killer feature of an Eclipse plugin like m2e/IvyDE.)