<ExtensionPoint> can be littered throughout plugins and GUI code, it would be nice to have a way to "flick a switch" and have the UI show up all places where an extension point exists, so a plugin developer can find out where to hook a component.

      Another option would be to crawl the code for all declarations of extension points as part of the build and generate an artifact that can be published.

          [JENKINS-35842] Allow ExtensionPoint's to be enumerated

          James Dumay added a comment -

          This is a really good idea

          James Dumay added a comment - This is a really good idea

          I had this idea to be able to configure extensionPoint implementations in a kind of personalize mode.

          You could get a dropdown which shows the "known implementations" of an ExtensionPoint and choose which ones you want to activate. However that leads to some kind of storage where we save the selection for the user.

          Thorsten Scherler added a comment - I had this idea to be able to configure extensionPoint implementations in a kind of personalize mode. You could get a dropdown which shows the "known implementations" of an ExtensionPoint and choose which ones you want to activate. However that leads to some kind of storage where we save the selection for the user.

            Unassigned Unassigned
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: