[
http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202743#action_202743
]
Body Mass commented on SCM-261:
-------------------------------
Sorry for the delay. I think the problem is more broad. I could have two
objects with the same name version, type, but differing only by instance id
(directories are most common example in the java world, but is a valid concept
for projects). This can happen when not using DCM at all, but it absolutely
*will* happen with DCM turned on.
I could be wrong, but I think if the SCM URL would take an optional instance
identifier it would fix the issue for all cases rather than just trying to fix
the DCM problem. If the user does not specify the instance id, then it defaults
to 1 if the user does not specify it. I think putting the burden on the user to
figure out the instance string (and possibly database ID and dcm delimiter) for
their projects would be reasonable.
That being said, I took a look at the source a long time ago but I didn't have
time to continue investigation.
> Synergy provider assumes instance of 1 for projects... won't work for
> distributed CM (and some other scenarios)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SCM-261
> URL: http://jira.codehaus.org/browse/SCM-261
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-synergy
> Affects Versions: 1.0-beta-4
> Environment: All Synergy environments
> Reporter: Body Mass
> Fix For: future
>
>
> We've started testing and hit our first snag:
> A unique locator in synergy is: <name>~<version>:<type>:<instance>
> The new snergy provider appears to assume thie instance is 1, and cannot find
> projects whose instance is not 1. This is not a valid for a Distributed CM
> install, for example, where 1 cannot be the instance number as Synergy will
> not allow it. This instance can be any string, and should be specified in the
> SCM URL or some other appropriate configuration mechanism.
> For example following is a query that works against my developer workspace.
> This same funkiness for DCM also applies to task names, but I can't get that
> far in testing due to the project problem.
> ccm> query -u
> is_task_in_folder_of(is_folder_in_rp_of('Arc_Workspace~k1gmd00:project:arc#1'))
> arc#6602 completed k1gmd00 task <void> arc <void>
> arc#6607 completed k1gmd00 task <void> arc <void>
> arc#6619 completed k1jcs01 task <void> arc <void>
> arc#6620 completed k1jcs01 task <void> arc <void>
> arc#6630 completed k1gmd00 task <void> arc <void>
> arc#6632 completed k1gmd00 task <void> arc <void>
> arc#6634 completed k1jcs01 task <void> arc <void>
> arc#6637 completed k1gmd00 task <void> arc <void>
> arc#6638 completed k1gmd00 task <void> arc <void>
> arc#6644 completed k1jcs01 task <void> arc <void>
> arc#6645 completed k1jcs01 task <void> arc <void>
> arc#6646 completed k1gmd00 task <void> arc <void>
> arc#6647 completed k1jcs01 task <void> arc <void>
> arc#6648 completed k1gmd00 task <void> arc <void>
> arc#6649 completed k1jcs01 task <void> arc <void>
> arc#6652 completed k1gmd00 task <void> arc <void>
> arc#6656 completed k1gmd00 task <void> arc <void>
> arc#6657 completed k1jcs01 task <void> arc <void>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
