[JIRA] (JENKINS-16228) ProjectNamingStrategy/UI: move "force existing" option to feature level

[alb...@folk.de (JIRA)]

Harald Albers created JENKINS-16228 ProjectNamingStrategy/UI: move "force existing" option to feature level Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 30/Dec/12 1:50 PM Description: 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. Project: Jenkins Priority: Minor Reporter: Harald Albers

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira