Grails
  1. Grails
  2. GRAILS-6597

Support declaring a plugin as deprecated

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      See: http://www.pubbs.net/201008/grails/10120-grails-dev-mechanism-for-deprecating-plugins.html

      This discussion is about a mechanism for declaring a plugin as deprecated, and optionally suggesting an alternative. The proposed mechanism is:

      class SomeCrustyPlugin {
          ...
          def deprecated = "This is the deprecation message"
          ...
      }
      

      and...

      class SomeCrustyPlugin {
          ...
          def deprecated = true
          ...
      }
      

      This would be read at plugin install time and an appropriate message displayed to the user. It doesn't prevent the user from using the plugin in anyway.

        Activity

        Hide
        Jeff Scott Brown added a comment -

        Is there a benefit to using a property like this and not using Java's @Deprecated?

        Show
        Jeff Scott Brown added a comment - Is there a benefit to using a property like this and not using Java's @Deprecated?
        Hide
        Luke Daley added a comment -

        Only that it's not rich enough, you can't specify any extra information on why it's deprecated or what should be used instead.

        Show
        Luke Daley added a comment - Only that it's not rich enough, you can't specify any extra information on why it's deprecated or what should be used instead.

          People

          • Assignee:
            Unassigned
            Reporter:
            Luke Daley
          • Votes:
            6 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Last Reviewed:

              Development