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

ProjectNamingStrategy/UI: move "force existing" option to feature level

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None

      The force existing option makes sense for any pattern naming strategy. Instead of requiring any implementor to take care about it, it should be moved from the Pattern strategy to the Restrict project naming feature's level.
      In order for the error messages to work, a new property like e.g. errorMessageLabel or toString has to be added to the extension's interface, which could default to the implementation's simple class name.

            integer Kanstantsin Shautsou
            albers Harald Albers
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: