Tapestry
  1. Tapestry
  2. TAPESTRY-2240

Groovy classes can no longer be used as component classes because of the public metaClass field

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.0.10
    • Fix Version/s: 5.0.11
    • Component/s: None
    • Labels:
      None

      Description

      Groovy classes always have a public field named metaClass, and Tapestry no treats that as an error and not a warning.

        Activity

        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Fix Version/s 5.0.11 [ 12312968 ]
        Resolution Fixed [ 1 ]
        Status In Progress [ 3 ] Closed [ 6 ]
        Howard M. Lewis Ship made changes -
        Summary Groovy classes can no longer be used a component classes because of the public metaClass field Groovy classes can no longer be used as component classes because of the public metaClass field
        Mark Thomas made changes -
        Workflow jira [ 12425254 ] Default workflow, editable Closed status [ 12568629 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568629 ] jira [ 12591662 ]

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development