On 19/11/2010, at 9:14 PM, richardm wrote:
>
> I updated to use from sourceSets.main.runtimeClasspath.filter { it.isFile() }
> and my JAR files are now included. Thanks.
>
> I've voted for the Jira issue, thanks for the link.
>
> I attempted your suggestion with the custom configuration, however my
> dependancy couldn't be resolved. I ran with -d and can see the JAR I have
> specified is in the compile classpath, but isn't getting resolved. The
> depedancy I've set is on :ca_client which is a JAR (ca_client.jar) produced
> by a dependant project and is on the compile classpath for this task. Have
> I specified the dependancy correctly?
>
>
> configurations {
> actualJars
> compile.extendsFrom actualJars
> }
>
> dependencies {
> compile project(':gui')
> compile ":j2ee", ":log4j" //picked up from repository defined in
> 'subprojects' section
> actualJars ':ca_client'
If 'ca_client' is another project in the same build, you'll need to do
something like:
dependencies {
....
actualJars project(':ca_client')
}
btw, the configuration doesn't have to be called 'actualJars', that was just an
example - it can be pretty much whatever you like.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
