|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I don't get your argumentation on maven parent pom for scm-sync implementors. If scm-sync expose an extension point, just need to create a very classic jenkins plugin and implement @Extension, what else ?
for backward compatibility, scm-sync could have the scm-sync-svn-provider and scm-sync-git provider bundled as dependency.
Initial implementation for those two plugins just need to extract code from scm-sync "as is" still using maven-scm, then let maintainer explore alternative implementation, either as improvements or in other dedicated plugins.