Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40759

clarify use of structs-plugin and org.jenkins-ci:symbol-annotation for new @Symbol definition

    Details

    • Similar Issues:

      Description

      (1) describes that one should use the structs-plugin to add @Symbol to an extension point, but at (2) an other approach is described: one should use org.jenkins-ci:symbol-annotation. Which is correct? What are the benefits of one over the other? Why should I use (1) instead of (2)?

      (1) https://wiki.jenkins-ci.org/display/JENKINS/Structs+plugin
      (2) https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#defining-symbols

        Attachments

          Activity

          Hide
          jglick Jesse Glick added a comment -

          You should depend on the structs plugin. That document is wrong.

          Show
          jglick Jesse Glick added a comment - You should depend on the structs plugin. That document is wrong.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Jesse Glick
          Path:
          DEVGUIDE.md
          http://jenkins-ci.org/commit/pipeline-plugin/14425eddb7cba82d5b403e9b46bf38e982734235
          Log:
          JENKINS-40759 Should depend on the structs plugin, not the library

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: DEVGUIDE.md http://jenkins-ci.org/commit/pipeline-plugin/14425eddb7cba82d5b403e9b46bf38e982734235 Log: JENKINS-40759 Should depend on the structs plugin, not the library
          Show
          jglick Jesse Glick added a comment - https://github.com/jenkinsci/pipeline-plugin/commit/14425eddb7cba82d5b403e9b46bf38e982734235

            People

            • Assignee:
              jglick Jesse Glick
              Reporter:
              imod Dominik Bartholdi
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: