Mathias,
Maybe I misunderstand your question, but there is a provided property of a
dependency. For example I'm working on an Android library, and I need to
compile against Android jar, but it is also built into the runtime. So I can
do this:
dependencies {
compile
I'd also be interested in this feature, so I've created Jira issue
http://jira.codehaus.org/browse/GRADLE-1289.
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Gradle-first-steps-and-create-project-tp3315373p3329214.html
Sent from the gradle-user mailing list archive at
I've been corrected by a coworker. The provided option I mentioned is a custom
feature we use in our build scripts, and is not part of Gradle. Apologies for
the inconvenience.
-Roy
On Jan 5, 2011, at 9:47 AM, Roy Clarkson wrote:
Mathias,
Maybe I misunderstand your question, but there
The eclipse plugin generates an output folder for eclipse projects
that points to the same build location as gradle uses. I'm not a fan
of mixing classes from Javac and the eclipse compiler, in part because
the eclipse compiler will compile just about anything and create a
runtime exception
This was my first attempt at resolving this issue but I was unsuccessful in
achieving the goal. I added the following code block to try to set this:
eclipseClasspath {
defaultOutputDir = new File(project.getProjectDir().getAbsolutePath()
+ /eclipseBin);
}
What I get as a
Thanks again Rene. This works!
Now if I could only figure out a way to rename the project.name so that the
resolved ivy file gets published with a different name to match the same
pattern as the rest of my artifacts. When I try to override project.name I get
Cause: Cannot set the value of
On Wed, Jan 5, 2011 at 11:01, Roy Clarkson rclark...@vmware.com wrote:
I've been corrected by a coworker. The provided option I mentioned is a
custom feature we use in our build scripts, and is not part of Gradle.
Apologies for the inconvenience.
-Roy
On Jan 5, 2011, at 9:47 AM, Roy
On Wed, Jan 5, 2011 at 11:39, Munoz, Pablo [Tech] pablo.mu...@gs.com wrote:
Thanks again Rene. This works!
Now if I could only figure out a way to rename the project.name so that the
resolved ivy file gets published with a different name to match the same
pattern as the rest of my
Hi,
I am using gradle to build my project for which I am also developing a
plugin. I started to use buildSrc as it seems to be the easiest approach.
The plugin has external jar dependencies and also depends on the 'root'
project classes. It took me some time to figure out that buildSrc can have
I'm encountering a problem where a copy task intermittently doesn't copy and
instead skips with UP-TO-DATE. I am having a hard time looking into the
problem because it happens so rarely. It has happened on a number of
different machines, though only very rarely.
The task copies a directory and
task create-dirs {
sourceSets.all*.java.srcDirs*.each { it.mkdirs() }
sourceSets.all*.resources.srcDirs*.each { it.mkdirs() }
}
I am wondering why not this code be available in all Plugins, once i apply a
plugin i get a ready made command to create the strucutre :)
--
View this
at lease this code be available as a ready made command in all plugins!
task create-dirs {
sourceSets.all*.java.srcDirs*.each { it.mkdirs() }
sourceSets.all*.resources.srcDirs*.each { it.mkdirs() }
}
--
View this message in context:
12 matches
Mail list logo