Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-1723

impossible to acquire lock problem when resolving dependencies

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: 1.0-milestone-4
    • Fix Version/s: 1.0-milestone-5

      Description

      Symptom

      A typical console output when this error occurs:

                             ::::::::::::::::::::::::::::::::::::::::::::::
      
                             ::          UNRESOLVED DEPENDENCIES         ::
      
                             ::::::::::::::::::::::::::::::::::::::::::::::
      
                             :: org.grails#grails-docs;1.3.6: not found
      
                             ::::::::::::::::::::::::::::::::::::::::::::::
      
      
             :::: ERRORS
                     impossible to acquire lock for org.grails#grails-docs;1.3.6
      
                     impossible to acquire lock for org.grails#grails-docs;1.3.6
      
                     impossible to acquire lock for org.grails#grails-docs;1.3.6
      
                     impossible to acquire lock for org.grails#grails-docs;1.3.6
      

      Workaround

      With the build not running, see if you have any .lck files anywhere under $homeDir/caches/artifacts. You should delete these - if they are present Ivy will complain that it cannot acquire the lock. It looks like ivy/wharf is not always cleaning these up when the build process exits.

        Attachments

          Activity

            People

            Assignee:
            adammurdoch Adam Murdoch
            Reporter:
            szczepiq Szczepan Faber
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: