[jira] Updated: (SCM-261) Synergy provider assumes instance of 1 for projects... won't work for distributed CM (and some other scenarios)

[ http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subir S updated SCM-261: Attachment: SCM-261-505-maven-scm-site.patch Site update for 505 and 261 Synergy provider assumes instance of 1 for

[jira] Updated: (SCM-261) Synergy provider assumes instance of 1 for projects... won't work for distributed CM (and some other scenarios)

[ http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-261: - Fix Version/s: (was: future) 1.3 Assignee: Olivier Lamy Synergy provider assumes

[jira] Updated: (SCM-261) Synergy provider assumes instance of 1 for projects... won't work for distributed CM (and some other scenarios)

[ http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subir S updated SCM-261: Attachment: SCM-261-maven-scm.patch Patch for this issue. Tested with Windows and Linux. Works fine with Windows. Testing

[jira] Updated: (SCM-261) Synergy provider assumes instance of 1 for projects... won't work for distributed CM (and some other scenarios)

[ http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-261: - Fix Version/s: future Synergy provider assumes instance of 1 for projects... won't work for