My response is based on the assumption that you are not using a binary repository and instead pulling jars from a directory. If that is not true, ignore this post. :)
You can work around this problem by using a flat directory resolver (I don't remember the syntax, but check out the user's guide). When specifying the resolver, you give it a pattern string that is used to match individual files. If you have the resolver ignore the version setting it will work. Sort of. The problem is not Gradle, but rather that you now have no version information. If you add a new library that says it needs commons-collections version 1.5 (because 1.4 doesn't have the functionality it needs), your flat dir resolver will find the commons-collections.jar and assume it's 1.5 when it's not. This will lead to compile issues, or (much) worse, weird run time issues. So, I would suggest the "ignore the version" solution as a short term solution until you can get to renaming those jars to have version information. Longer term, that is much safer. -- John Murph Automated Logic Research Team
