|
||||||||
|
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... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (JIRA)
- [JIRA] (JENKINS-16342) asynchPeople ve... [email protected] (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.