On 22/10/2010, at 1:09 PM, Thomas R. Corbin wrote:
> On Fri, 2010-10-22 at 11:49 +1100, Adam Murdoch wrote:
>> On 21/10/2010, at 2:06 AM, Thomas R. Corbin wrote:
>>
>>>
>>> I've been trying:
>>>
>>> compileGroovy.options.listFiles = true
>>> compileGroovy.options.verbose = true
>>> compileGroovy.groovyOptions.listFiles = true
>>> compileGroovy.groovyOptions.verbose = true
>>>
>>> but none of it seems to work.
>>
>>
>> You should use:
>>
>> compileGroovy.groovyOptions.listFiles = true
>
> Ah, see I was doing that, but I didn't realize I needed the -i option.
>
> The problem with the -i option is that I get all kinds of stuff I don't
> want.
>
>>
>> The file names are logged at info level, so you need to run Gradle
>> with the -i command-line option to see them.
>>
>> Alternatively, you can just write some code to list them:
>>
>> compileGroovy.doFirst {
>> source.each { File f ->
>> println f
>> }
>> }
>>
>> This will work without needing the -i option.
>
> Yes, but this just lists all the source in the source tree, not just the
> source files that are going to be compiled.
This should print out just the files that are going to be compiled by the
compileGroovy task. Are you seeing something different?
>
> I sure would like a way to see what's triggering actions w/o having to
> poke through enormous amounts of logging.
There's a few things you might be referring to by 'what's triggering actions',
so I'm not entirely sure what you need. Could you give some details about the
problem you're having where you want to see a list of the source files?
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
