|
||||||||
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 |
- [JIRA] (JENKINS-16342) asynchPeople very sl... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... dogf...@java.net (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... vjura...@java.net (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... jgl...@cloudbees.com (JIRA)
> SubversionMailAddressResolverImpl should probably be rewritten to perform its calculations in a long-running process and cache them. Or maybe this should just be deleted and the problem solved in a different way.
Absolutely +1 for deleting this - as well as in all other SCM plugin where something analogue is implemented!
These MailAddressResolvers are implemented in a so ridiculous inefficient way and their usefulness is IMHO very very limited.