Actually this doesn't make sense. The task "Android SDK: Resolving error markers" is a job because this is guaranteed to be executed when the workspace can be changed. I'm not sure why it would block and do nothing.
(if the workspace was locked, then an exception would be thrown and the job would finish early instead of blocking) However at the end of the job, a refresh is call and this is what I'm thinking is failing to finish. I'm not sure why to be honest. Xav On Thu, Jan 27, 2011 at 9:47 AM, TreKing <[email protected]> wrote: > On Tue, Jan 25, 2011 at 12:04 PM, paul french <[email protected]> > wrote: >> >> Any ideas what the problem might be? > > Going here leads to here, which indicates that: > // In some cases, the workspace may be locked for modification when we > // pass here. > // We schedule a new job to put the marker after. > So make sure your workspace is not locked for modification (i.e., it's > writable on disk). Why they don't put this in the error itself is beyond me. > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered devices > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- 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 "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
