If by normal you mean regular compile dependencies on artifacts, the normal dependency declarations had the specific [group]:[artifact]:[version]:[type] format, and not many of the jars in the common directory had these conventions. Just based on the name, unmanagedClasspath seemed to make more sense. The common directory, as of yet, is just a local directory with a big pile of unmanaged and mostly unversioned jars . If there is a way to declare a normal dependency of each project on the jars in that directory without versioning all of the jars and/or listing them all individually (there are 100+), I would be interested to know.
As far as the issue goes, it was solved in two steps. First, I got a lot of help creating a task to add the jars and making each projects compile task depend on that task. This worked. We found that there was come quirky context issue where it was adding the jars to different classpaths than expected (probably the same one each time). Then, earlier today, I tried to revert back so I could describe the problem to you more effectively, and all I left in was compile.unmanagedClasspath(jars) in the allprojects section and everything worked. I had moved some other things into allprojects, so it's possible that things were happening in the wrong order, but it works now and it makes as much sense as I thought it should when I was having problems before. -- View this message in context: http://www.nabble.com/gradlefile-cleaning--tp17650512p17695093.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
