On 18/01/2013, at 8:06 PM, Adam Murdoch <[email protected]> wrote:

> 
> On 18/01/2013, at 9:03 PM, Luke Daley wrote:
> 
>> http://issues.gradle.org/browse/GRADLE-2531
>> 
>> Does anyone have an explanation for this?
> 
> It's because the JavaCompile task has a @SkipWhenEmpty on its source files 
> (via the SourceTask), so that when you remove all the source files the task 
> is skipped and it doesn't remove all the stale class files, as it would if 
> you, say, removed all but one of the source files. There's a jira issue for 
> this somewhere, but I can't find it.

Found it: http://issues.gradle.org/browse/GRADLE-2579

Closing the other as a duplicate.

-- 
Luke Daley
Principal Engineer, Gradleware 
http://gradleware.com


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to