Also, I'm running:
- Studio 1.1 Beta 2
- Android Gradle plugin 1.0.1
- Multidex
On Tuesday, 3 February 2015 14:15:21 UTC+13, Josh Burton wrote:
>
> In this instance I had edited both java and layout files. I should also
> mention that for this project we define custom source sets - perhaps this
> is contributing to the issue?
>
> sourceSets {
> main.java.srcDirs = ['src-ui/main/java', 'src/main/java']
> main.res.srcDirs = ['src-ui/main/res', 'src/main/res']
> main.assets.srcDirs = ['src-ui/main/assets', 'src/main/assets']
> ....
> }
>
>
> The files I edited were located in src-ui/main/java and
> src-ui/main/res/layout.
>
> On Tuesday, 3 February 2015 14:02:53 UTC+13, Xavier Ducrohet wrote:
>>
>> Which files have you edited? Where are they located, what's their type
>> (java, res, manifest, ...) ?
>>
>> On Mon, Feb 2, 2015 at 4:25 PM, Josh Burton <[email protected]> wrote:
>>
>>> Hi Xavier thanks for the reply.
>>>
>>> I've just run into the issue again and run a command line build with
>>> --info.
>>>
>>> The full (slightly edited) log is below, but it does seem like gradle
>>> isn't recognising that files have changed, and is skipping the assemble
>>> tasks.
>>>
>>>
>>> :app:processDebugResources took 1544ms
>>> :app:processDebugResources (Thread[main,5,main]) completed. Took 1.544
>>> secs.
>>> :app:generateDebugSources (Thread[main,5,main]) started.
>>> :app:generateDebugSources
>>> Skipping task ':app:generateDebugSources' as it has no actions.
>>> :app:generateDebugSources took 0ms
>>> :app:generateDebugSources (Thread[main,5,main]) completed. Took 0.012
>>> secs.
>>> :app:compileDebugJava (Thread[main,5,main]) started.
>>> :app:compileDebugJava
>>> Skipping task ':app:compileDebugJava' as it is up-to-date (took 0.14
>>> secs).
>>> :app:compileDebugJava UP-TO-DATE
>>> :app:compileDebugJava took 144ms
>>> :app:compileDebugJava (Thread[main,5,main]) completed. Took 0.145 secs.
>>> :app:preDexDebug (Thread[main,5,main]) started.
>>> :app:preDexDebug
>>> Skipping task ':app:preDexDebug' as it is up-to-date (took 0.016 secs).
>>> :app:preDexDebug UP-TO-DATE
>>> :app:preDexDebug took 19ms
>>> :app:preDexDebug (Thread[main,5,main]) completed. Took 0.02 secs.
>>> :app:dexDebug (Thread[main,5,main]) started.
>>> :app:dexDebug
>>> Skipping task ':app:dexDebug' as it is up-to-date (took 0.097 secs).
>>> :app:dexDebug UP-TO-DATE
>>> :app:dexDebug took 98ms
>>> :app:dexDebug (Thread[main,5,main]) completed. Took 0.098 secs.
>>> :app:crashlyticsStoreDeobsDebug (Thread[main,5,main]) started.
>>> :app:crashlyticsStoreDeobsDebug
>>> Executing task ':app:crashlyticsStoreDeobsDebug' (up-to-date check took
>>> 0.0 secs) due to:
>>> Task has not declared any outputs.
>>> :app:crashlyticsStoreDeobsDebug took 34ms
>>> :app:crashlyticsStoreDeobsDebug (Thread[main,5,main]) completed. Took
>>> 0.035 secs.
>>> :app:crashlyticsUploadDeobsDebug (Thread[main,5,main]) started.
>>> :app:crashlyticsUploadDeobsDebug
>>> Executing task ':app:crashlyticsUploadDeobsDebug' (up-to-date check took
>>> 0.0 secs) due to:
>>> Task has not declared any outputs.
>>> :app:crashlyticsUploadDeobsDebug took 32ms
>>> :app:crashlyticsUploadDeobsDebug (Thread[main,5,main]) completed. Took
>>> 0.032 secs.
>>> :app:fabricCleanupResourcesAfterUploadDebug (Thread[main,5,main])
>>> started.
>>> :app:fabricCleanupResourcesAfterUploadDebug
>>> Executing task ':app:fabricCleanupResourcesAfterUploadDebug' (up-to-date
>>> check took 0.0 secs) due to:
>>> Task has not declared any outputs.
>>>
>>> :app:fabricCleanupResourcesAfterUploadDebug took 34ms
>>> :app:fabricCleanupResourcesAfterUploadDebug (Thread[main,5,main])
>>> completed. Took 0.034 secs.
>>> :app:compileDebugNdk (Thread[main,5,main]) started.
>>> :app:compileDebugNdk
>>> Skipping task ':app:compileDebugNdk' as it is up-to-date (took 0.007
>>> secs).
>>> :app:compileDebugNdk UP-TO-DATE
>>> :app:compileDebugNdk took 10ms
>>> :app:compileDebugNdk (Thread[main,5,main]) completed. Took 0.01 secs.
>>> :app:processDebugJavaRes (Thread[main,5,main]) started.
>>> :app:processDebugJavaRes
>>> Skipping task ':app:processDebugJavaRes' as it has no source files.
>>> :app:processDebugJavaRes UP-TO-DATE
>>> :app:processDebugJavaRes took 1ms
>>> :app:processDebugJavaRes (Thread[main,5,main]) completed. Took 0.002
>>> secs.
>>> :app:validateDebugSigning (Thread[main,5,main]) started.
>>> :app:validateDebugSigning
>>> Executing task ':app:validateDebugSigning' (up-to-date check took 0.0
>>> secs) due to:
>>> Task has not declared any outputs.
>>> :app:validateDebugSigning took 2ms
>>> :app:validateDebugSigning (Thread[main,5,main]) completed. Took 0.023
>>> secs.
>>> :app:packageDebug (Thread[main,5,main]) started.
>>> :app:packageDebug
>>> :app:packageDebug took 3297ms
>>> :app:packageDebug (Thread[main,5,main]) completed. Took 3.299 secs.
>>> :app:zipalignDebug (Thread[main,5,main]) started.
>>> :app:zipalignDebug
>>> :app:zipalignDebug took 220ms
>>> :app:zipalignDebug (Thread[main,5,main]) completed. Took 0.22 secs.
>>> :app:assembleDebug (Thread[main,5,main]) started.
>>> :app:assembleDebug
>>> Skipping task ':app:assembleDebug' as it has no actions.
>>> :app:assembleDebug took 1ms
>>> :app:assembleDebug (Thread[main,5,main]) completed. Took 0.001 secs.
>>>
>>>
>>>
>>> On Tuesday, 3 February 2015 07:18:54 UTC+13, Xavier Ducrohet wrote:
>>>>
>>>> You could try to build from the command line with --info to see what
>>>> the tasks says about its input/output.
>>>>
>>>> If the task runs because its input changed but the output didn't
>>>> change, ie the next task in the chain doesn't see its input as having
>>>> changed (gradle checks for content via checksum rather than timestamp),
>>>> then it means that the task doesn't properly handle its incremental mode
>>>> and it's a bug. Please let us know.
>>>>
>>>> On Sun, Feb 1, 2015 at 6:44 PM, Josh Burton <[email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I've run into an issue with one project I'm working on. Fairly often I
>>>>> build, but don't see any changes the build (even though I've made changes
>>>>> in Java and XML).
>>>>>
>>>>> I'm forced to clean the project and rebuild, and I'll then see then
>>>>> changes in the built apk.
>>>>>
>>>>> Can anyone point me in the right direction for trying to troubleshoot
>>>>> why this might be happening?
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "adt-dev" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Xavier Ducrohet
>>>> Android SDK Tech Lead
>>>> Google Inc.
>>>> http://developer.android.com | http://tools.android.com
>>>>
>>>> Please do not send me questions directly. Thanks!
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "adt-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Xavier Ducrohet
>> Android SDK Tech Lead
>> Google Inc.
>> http://developer.android.com | http://tools.android.com
>>
>> Please do not send me questions directly. Thanks!
>>
>
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
