|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Regarding the JENKINS-17384...
It's just a top-level use-case.
Listener should not provide callbacks to manage columns directly. It should just notify implementations that something has changed in Views.
1) User creates a new view
2) ViewListener fires the onCreated(View view) event
3) The "DefaultColumnsViewListener" from a plugin catches the event, alters the configuration and then saves the view
4) Other ViewListeners do other actions
Actually, such approach is not required for JENKINS-17378, but it could be used for more complex cases