On 05/07/2011, at 2:09 AM, Wilson MacGyver wrote:

> Can gradle wrapper task be used when your project uses plugin that
> didn't come with gradle disto itself?
> 
> I'm using clojure plugin for gradle.
> 
> after I added
> 
> task wrapper(type: Wrapper) {
>    gradleVersion = '0.9.2'
> }
> 
> 
> in my build.gradle
> 
> when I run gradle wrapper

Do you mean here that the failure happens when you run 'gradle wrapper' to 
generate the wrapper, or that the failure happens when you run the generated 
'gradlew' script?

If it's 'gradle wrapper' that's failing, what does gradle -v give you?

If it 'gradlew' that's failing, you might check that the version of the 
clojuresque plugin that you're using supports Gradle 0.9.2 because, from the 
failure, it looks like it's trying to use a method added in one of the Gradle 
1.0 milestones.


> 
> it gives
> 
> Build file error at line: 11
> 
> * What went wrong:
> A problem occurred evaluating root project 'ctest'.
> Cause: No signature of method:
> org.gradle.api.internal.file.UnionFileTree.source() is applicable for
> argument types:
> (org.gradle.api.internal.file.DefaultSourceDirectorySet) values: [main
> Clojure source]
> Possible solutions: use([Ljava.lang.Object;)
> 
> line 11 is
> 
> apply {
>    plugin 'clojure'
> }
> 
> 
> the only other odd thing I can think of is, I'm pulling in the plugin by doing
> 
> buildscript {
>  repositories {
>    mavenRepo name: 'clojars', urls: 'http://clojars.org/repo'
>  }
>  dependencies {
>    classpath 'clojuresque:clojuresque:1.4.1'
>    classpath 'clojuresque:runtime:1.4.1'
>  }
> }
> 
> 
> Thanks
> 
> 
> -- 
> Omnem crede diem tibi diluxisse supremum.
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>    http://xircles.codehaus.org/manage_email
> 
> 


--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com

Reply via email to