Hi Rafa,
apologies for missing your posting and for the late response.
On Oct 24, 2008, at 4:54 PM, Rafael Serrano wrote:
Hi all,
I'm using the eclipse task to automatically generate .project
and .classpath
files and it works fine. However, my goal is to create eclipse
projects that
can be shared among different users, so I'd like to tweak the default
behaviour of gradle in order to:
1.- Have my dependencies copied into an specified directory
2.- Make .classpath point to the libraries in that directory, but
not those
in MY_HOME_FOLDER/.gradle/cache/foo
How can I configure gradle to do these things?
I have already workarounded the first point with something like this:
dependencies.resolve("runtime").each {
file -> FileUtils.copyFileToDirectory(file, webInfLibDir)
}
but I'm sure it exists a more elegant way to get it done :)
Not really. If you are using remote repositories, the plugin assumes
that the normal use case is to use the dependencies from the cache.
Other eclipse users for your project could use Gradle to generate the
Eclipse classpath (during this process the dependencies get
downloaded to the cache). Yo make it easier for them to use Gradle,
you might use the Gradle wrapper, so that they don't need to have
Gradle installed for using Gradle.
But I see your use case and the problem that this is not possible to
configure the Eclipse generation in the way you need it. There is an
issue for this: http://jira.codehaus.org/browse/GRADLE-196
Another possibility is to use non-remote repositories (look for
FlatDirResolver in the user's guide). In this case the cache is
circumvented and the libs might be in the subdir of the PROJECT_ROOT.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
