Hans Dockter wrote:
>
> On Fri, Mar 26, 2010 at 8:36 PM, mjparme <[email protected]> wrote:
>
> Gradle can only deal with file collections as arguments for a
> configuration.
>
> dependencies {
> runtime files(fileTree(...))
> }
>
> The logic behind that behavior is that a file tree preserves the hierarchy
> whereas a file collection is a flat list of file. The files method
> flattens
> a file tree. But this is such a common scenario, that we should accept
> file
> trees as well and automatically turn them into a file collection.
>
> - Hans
>
> --
> Hans Dockter
> Founder, Gradle
> http://www.gradle.org, http://twitter.com/gradleorg
> CEO, Gradle Inc. - Gradle Training, Support, Consulting
> http://www.gradle.biz
>
>
Thanks for the response. I changed it to uses files(fileTree(...)) like you
mentioned and it still can't compile any classes that depend on classes in
the jars in lib. Maybe I misunderstood the solution, this is what I changed
it to:
dependencies {
runtime files(fileTree(dir: 'lib', includes: ['*.jar']))
}
ClientAuthenticator.java:29: cannot find symbol
symbol : class Logger
location: class redacted.client.request.actions.ClientAuthenticator
private static Logger logger =
Logger.getLogger(ClientAuthenticator.class);
log4j-1.2.15.jar is in my lib directory.
As a side note, all the documentation I have found (UserGuide and samples in
the distribution) seems to assume everyone uses dependency management. There
is very little documentation (actually none) about how to add jars from a
project path to the compiler's classpath.
--
View this message in context:
http://old.nabble.com/Compile-using-jars-from-a-lib-directory-tp28047035p28047471.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
