Merlyn,
Here is a very concise example, not quite the absolute shortest
though.======================================package levi.profiler.example;/**
Tue Jul 12, 2011 Shows that the gradle task 'compileGroovy' does not
stop the build. (may be using gradle wrong?)*/class
UncompilableGroovyClass{ ]}======================================
When I do compileGroovy, this is output, but it proceeds and doesn't halt the
build.
======================================:compileJavaNote: Some input files use or
override a deprecated API.Note: Recompile with -Xlint:deprecation for
details.Note: Some input files use unchecked or unsafe operations.Note:
Recompile with -Xlint:unchecked for
details.:compileGroovyorg.codehaus.groovy.control.MultipleCompilationErrorsException:
startup failed,
X:\_core\code\levi\profiler\example\UncompilableGroovyClass.groovy: 10:
unexpected token: ] @ line 10, column 2. ] ^
1 error======================================
The build.gradle file resides in the _core directory and I have done this to
account for not using the "main/java" folder
layout:======================================sourceSets { main {
java.srcDir 'code' resources.srcDir 'fordeployment'
groovy.srcDir 'code' }}======================================
Any ideas?
thanks,Levi
__________________________________________
--- On Tue, 7/12/11, Merlyn Albery-Speyer <[email protected]>
wrote:
From: Merlyn Albery-Speyer <[email protected]>
Subject: Re: [gradle-user] compileGroovy???
To: [email protected]
Date: Tuesday, July 12, 2011, 10:33 AM
Hi Levi,
Could you help by posting the smallest Groovy class that demonstrates this
issue?
Cheers,
Merlyn
On Jul 12, 2011 4:03 AM, "Levi Yourchuck" <[email protected]> wrote:
> Hi all,
> I am wondering if this is the expected gradle behavior.
> When I run the compileJava task and I have an error in the .java code, it
> will cause the gradle build to halt and not execute further tasks.
> However when I have an error in some .groovy code, it will cause an error in
> the console output similar to compileJava but it does not stop the gradle
> build.
> This has the effect that when the jar task is chugging along, it does not
> have and .class files from a compileGroovy task to include and the subsequent
> build is broken but reports BUILD SUCCESSFUL.
> Is there something that I have to do when configuring the compileGroovy task
> in order to get this behavior? I am not seeing much for info on this in the
> docs.
> thanks,Levi
