Grails
  1. Grails
  2. GRAILS-9550

groovy.lang.MissingMethodException: No signature of method: org.gmock.internal.metaclass.MockProxyMetaClass$4.doCall()

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.2-RC2
    • Fix Version/s: 2.2.1
    • Component/s: None
    • Labels:
      None

      Description

      Moving from 2.1.1 to 2.2-RC2 I'm now seeing an issue with GMock. I thought it might be a groovy 2 issue, but I created a non grails project that used groovy 2.0.5 and was able to use GMock.

      project attached: just run "grails test-app" to get error.

        Activity

        Hide
        Graeme Rocher added a comment -

        fixing this will require upgrading to Groovy 2.0.6

        Show
        Graeme Rocher added a comment - fixing this will require upgrading to Groovy 2.0.6
        Hide
        ashu kumar singh added a comment - - edited

        whats the workaround for time being, if there is any ? as I am also facing the exact same problem and I am using grails 2.2.0 released version.

        Show
        ashu kumar singh added a comment - - edited whats the workaround for time being, if there is any ? as I am also facing the exact same problem and I am using grails 2.2.0 released version.
        Hide
        Graeme Rocher added a comment -

        don't use GMock, or wait for 2.2.1 when we will upgrade to Groovy 2.0.6

        Show
        Graeme Rocher added a comment - don't use GMock, or wait for 2.2.1 when we will upgrade to Groovy 2.0.6
        Hide
        ashu kumar singh added a comment -

        Thanks for the reply Graeme. Not using Gmock seems to be very expensive option as we will have to re work 500 odd unit tests, so waiting for 2.2.1 is the only option, do you know when is the next release scheduled for ?

        Show
        ashu kumar singh added a comment - Thanks for the reply Graeme. Not using Gmock seems to be very expensive option as we will have to re work 500 odd unit tests, so waiting for 2.2.1 is the only option, do you know when is the next release scheduled for ?
        Hide
        Graeme Rocher added a comment -

        fixed by upgrade to Groovy 2.0.6

        Show
        Graeme Rocher added a comment - fixed by upgrade to Groovy 2.0.6

          People

          • Assignee:
            Graeme Rocher
            Reporter:
            Mike Damman
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development