|
||||||||
|
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/groups/opt_out.
scm-sync-config to expose an extension point for all repo operation would indeed be a more extensible design.
I'm also not convinced about using maven-scm implementation. For sample, the git one don't let you create a commit passing author/committer identity. An alternate impl to use JGit could then be created. Afaik scm-sync only uses a limited set of scm methods, so such an implementation wouldn't be such a pain.