:D has…
dependencies {
testCompile project(':C').sourceSets.test.runtimeClasspath
}
If :C hasn't been evaluated yet, project(':C').sourceSets won't be the value
you want (I think it's actually going to silently return null).
That is the sourceSets property is added to the project(:C)
Thanks Guys! That worked.
I actually used this before but changed it because I was unable to make it
maven compatible or configure an ivy pattern.
But I guess it doesn't matter for now. :)
Cheers,
Vinod
On Mon, Jul 25, 2011 at 1:16 AM, Adam Murdoch [via Gradle]
It worked. Thanks René!
Perhaps Gradle could include this configuration as default considering that
WEB-INF/lib is the standard location for war libs.
Ricardo
--
View this message in context:
http://gradle.1045684.n5.nabble.com/War-packed-with-duplicated-jars-tp4624905p4631055.html
Sent from
Hi,
I just wrote my first gradle plugin to integrate a specific parser generator
into our builds. The parser generator uses velocity 1.6.2 and velocity has a
dependency to log4j 1.2.12.
Now as soon as the parser generator initializes velocity I am getting the
following exception:
Caused by:
I recently asked about a method to filter out custom jar tasks from
the assemble task for a custom gradle plugin I'm wriging. Basically I
need some jar tasks NOT to be executed by assemble.
I was directed by Luke to apply a filter by overriding the assemble
task. Here is my code - which is
For the record and for anybody facing similar problems:
I solved it by implementing velocity's LogChute interface so that velocity does
not implicitly assume that log4j has to be used.
Best regards
Alexander
On Jul 25, 2011, at 11:31 AM, Alexander von Zitzewitz wrote:
Hi,
I just wrote my
I think this solved my prob:
project.rootProject.allprojects.each {subproject -
On Mon, Jul 25, 2011 at 11:26 AM, phil swenson phil.swen...@gmail.com wrote:
I recently asked about a method to filter out custom jar tasks from
the assemble task for a custom gradle plugin I'm wriging.
I believe that simply using log4j 1.2.15 will also work (that's the minimum
log4j that works with the latest slf4j I believe).
-Spencer
--- On Mon, 7/25/11, Alexander von Zitzewitz a.zitzew...@hello2morrow.com
wrote:
From: Alexander von Zitzewitz a.zitzew...@hello2morrow.com
Subject: Re:
Greg, at this moment only tasks are exposed as build parameters in the
tooling api. So you cannot easily pass parameters. Can you file a jira
issue to address that?
Cheers!
On Fri, Jul 22, 2011 at 12:37 PM, Grzegorz Gigon greg.gi...@gmail.com wrote:
Thanks for that Rene
How do I pass the
Greg, at this moment only tasks are exposed as build parameters in the
tooling api. So you cannot easily pass parameters. Can you file a jira
issue to address that?
Cheers!
On Fri, Jul 22, 2011 at 12:37 PM, Grzegorz Gigon greg.gi...@gmail.com wrote:
Thanks for that Rene
How do I pass the
Hi All,
Ran into a problem using the new ivy() repository. Grabbing the latest
dependency using Ivy's version.+ no longer works. It works if I switch
back to a URLResolver! Any ideas?
E.g:
dependencies {
Default(group: 'my_group', name: 'my_module', version: *'2.0.0.+'*,
configuration:
Hey Merlyn,
Just to keep it documented, I got it working!!! Man, Gradle is awesome!
thanks a lot for your help... Here's the complete code for processing Java 6
Annotations with Javac compiler flags + dependencies expressed in Maven...
Is this a bug?
// The definition of jpa sourceSet WILL ONLY
12 matches
Mail list logo