On Sat, Dec 5, 2009 at 5:21 AM, Russel Winder <[email protected]>wrote:
> > Why is JUnit in the lib directory? Isn't the whole point of Maven/Ivy > that you download the dependencies on an as need basis into your local > cache? > > I suspect the answer is going to be Eclipse and/or IntelliJ IDEA -- > which says more about the IDEs that anything else ;-) > > JUnit is in the lib directory because Gradle has compile-time (and therefore run-time) dependencies on JUnit. So, unless you want Gradle to ship without any libs and then download them the first time it runs (which seems unnecessarily complex), there is not much to do. As for IDEs, I agree completely. IDEs have not kept up with the advent of binary repositories. This leads to weird workarounds like the "ide" task in Gradle. -- John Murph Automated Logic Research Team
