2009/8/17 Russel Winder <[email protected]>:
> I am beginning to think something very weird is happening deep in the
> bowels of Gradle/Groovy/Java/Bash.
>
> If I issue the gradlew command from the command line, the Gradle build
> works fine. If I put the gradlew command in a shell script or subshell,
> then I get the
>
>> > :compile
>> > org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
>> > failed,
>> > /home/users/russel/Repositories/Bazaar/Subversion/GradleCore/Trunk/src/main/groovy/org/gradle/api/internal/file/CopySpecImpl.groovy:
>> > 62: The return type of org.gradle.api.file.CopySpec
>> > from([Ljava.lang.Object;) in org.gradle.api.internal.file.CopySpecImpl is
>> > incompatible with org.gradle.api.file.CopySourceSpec
>> > from([Ljava.lang.Object;) in org.gradle.api.file.CopySourceSpec.
>> > Node: org.codehaus.groovy.ast.MethodNode. At [62:5] @ line 62, column 5.
>> > CopySpec from(Object... sourcePaths) {
>> > ^
>
> error. I checked the java command issued to do the compilation and it
> appears to be identical. This is where the weirdness happens: if the
> java command issued is the same how can the resulting groovyc execution
> do the right thing from a shell and the wrong thing from a subshell?
Could it be that your environment variables are different in the shell
and the subshell? I know that in bash login shells are treated
differently. If you are using bash you could try starting the subshell
with the '-l' switch to make it act as a login shell.
/grydholt
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
