[
http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203772#action_203772
]
Subir S commented on SCM-261:
-----------------------------
Body Mass,
My assumption about DCM in step b.) above was wrong. I noticed that instance of
a project (generically object) need not be same as the local database. It can
be that of the remote database also. Secondly even in DB where there is no DCM
in use instance need not be default 1. It can also change.
So i fixed this as per your suggestion. Such that in the SCM URL the last or
6th parameter is an optional (instance). If specified then its used, else
default value of '1' is used, so that current users do not get affected.
It works fine with Windows environment. With Linux testing is not possible due
to a plexus-util issue. However that is not related to this case. I have
checked that construction of the argument is fine with Linux also.
I will submit a patch soon, so that this can be included to SCM 1.3
Thanks for your valuable comments.
> 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
