[jira] Commented: (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:comment-tabpanelfocusedCommentId=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
[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 in Linux not
possible due to [SCM-514|http://jira.codehaus.org/browse/SCM-514]
However that case is related to Quotes in arguments.
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
Attachments: SCM-261-maven-scm.patch
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
[jira] Commented: (SCM-514) Quotes in CommandLine is causing failure to scm:update
[
http://jira.codehaus.org/browse/SCM-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203776#action_203776
]
Subir S commented on SCM-514:
-
Created a issue with plexus-utils
[PLXUTILS-122|http://jira.codehaus.org/browse/PLXUTILS-122]
Quotes in CommandLine is causing failure to scm:update
--
Key: SCM-514
URL: http://jira.codehaus.org/browse/SCM-514
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-synergy
Affects Versions: 1.3
Environment: Platform OS: RHEL 5
Java: 1.6.0_17
Maven: 2.1.0
Maven SCM: 1.3-SNAPSHOT
SCM: CM/Synergy 7.0
Reporter: Subir S
Priority: Critical
While executing scm:update command in 'Linux', there is a single quote which
appears in the start and end of the argument. This causes the already
existing arguments to have wrong syntax.
mvn scm:update -Dusername=user -Dpassword=pass -X shows the following output:
[DEBUG] STDERR :
[DEBUG] Synergy : Entering getWorkingProject method
[DEBUG] Executing: /bin/sh -c ccm query -u -f %objectname {color:red}
-- additonal start single quote '{color}
owner='user' and status='working' and type='project' and
has_predecessor('sm-3.3:project:inhytest#1')' {color:red}
-- Additional end single quote{color}
[DEBUG] Exit code :1
[DEBUG] STDOUT : unavailable
[DEBUG] STDERR :Warning: Syntax error in query request: owner=user and
status=working and type=project and
has_predecessor(sm-3.3:project:inhytest#1) {color:red}
-- Note that now the single quotes after interpretation by the shell are
removed.{color}
This works fine in 'Windows' platform.
Correct output should be: /bin/sh -c ccm query -u -f %objectname
owner='user' and status='working' and type='project' and
has_predecessor('sm-3.3:project:inhytest#1') {color:red}
--No single quotes, but double quotes and inner single quotes not modified
then.{color}
How to get this working? I have seens some changes to plexus-utils on these
quotes, but could not understand how to workaround this. Please help.
--
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
[jira] Commented: (MRELEASE-505) Upgrade to scm 1.3
[ http://jira.codehaus.org/browse/MRELEASE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204982#action_204982 ] Subir S commented on MRELEASE-505: -- Yes, please. Since [SCM-505|http://jira.codehaus.org/browse/SCM-505] and [SCM-261|http://jira.codehaus.org/browse/SCM-261] are some critical fixes in maven-scm-snergy provider. Without which release cannot be done. Hence if release plugin is to be used then this should also be updated. Upgrade to scm 1.3 -- Key: MRELEASE-505 URL: http://jira.codehaus.org/browse/MRELEASE-505 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Reporter: Olivier Lamy Fix For: 2.0-beta-10 -- 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
[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 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
Assignee: Olivier Lamy
Fix For: 1.3
Attachments: SCM-261-505-maven-scm-site.patch, SCM-261-maven-scm.patch
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
[jira] Commented: (MRELEASE-516) release:prepare should support a nested/flat hybrid SCM structure
[
http://jira.codehaus.org/browse/MRELEASE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207710#action_207710
]
Subir S commented on MRELEASE-516:
--
Also the scm-tag of the parent pom is only available in the release.properties.
Modules get mostly the scm-tag as HEAD. This may not work with all VCS. I have
synergy and we also intend to use this flat structure due to maintanence
complexities.
I tried with -Dproject.scm.c.o.m\:module_child.tag=module_child-tagVersion
but that is not respected by release:prepare.
All the submodules have SCM elements declared separately in their POMs.
release:prepare should support a nested/flat hybrid SCM structure
-
Key: MRELEASE-516
URL: http://jira.codehaus.org/browse/MRELEASE-516
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: perform, prepare
Affects Versions: 2.0-beta-9
Environment: OS X 10.5.8, Windows XP Prof, JDK 1.5.0_12, SVN, GIT, CVS
Reporter: Eric Miles
Attachments: maven-release-issue.zip, odd-tags.png
This issue is related to MRELEASE-261 in that release prepare is having some
difficulty in dealing with certain SCM structures during the prepare goal.
Our project structure is flat as you would see in a typical IDE setup:
{noformat}
release-workspace\
|
|--release-parent
||+pom.xml (modules: ../release-module1, ../release-module2)
|
|--release-module1
||+pom.xml (parent: ../release-parent)
|
|--release-module2
|+pom.xml (parent: ../release-parent)
{noformat}
Our SCM (svn) structure is as follows:
{noformat}
svnroot
|
+--release-parent/trunk/pom.xml
+--release-parent/tags/release-parent-1.0.9/pom.xml
|
+--release-module1/trunk/pom.xml
+--release-module1/tags/release-module1-1.0.9/pom.xml
|
+--release-module1/trunk/pom.xml
+--release-module2/tags/release-module2-1.0.9/pom.xml
{noformat}
If we execute release:prepare with no configuration to the release plugin, we
get the following error:
{noformat}
[INFO] [INFO]
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd
/Users/emiles/Projects/release-workspace/release-parent svn
--non-interactive commit --file
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-1253932520.commit
--targets
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-4376558781490229966-targets
[INFO] Working directory:
/Users/emiles/Projects/release-workspace/release-parent
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{noformat}
If we use the 2.0-beta-10-SNAPSHOT with flat project support and provide the
-DcommitByProject=true JVM parameter, we do not get any errors, however
tagging does not happen as expected. Rather than having tags for each of the
projects, some odd tagging happened at the parent level where an entire
structure was created (with branches, tags and trunk under the tag folder).
I'm attaching a screen shot for reference.
Ignoring the fact that the prepare only somewhat worked, when I attempted to
perform the release, I get an error:
{noformat}
emiles-macbook:release-parent emiles$ mvn release:perform
-DcommitByProject=true
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO] Unnamed - com.captechventures:release-module1:jar:0.0.3-SNAPSHOT
[INFO] Unnamed - com.captechventures:release-module2:jar:0.0.3-SNAPSHOT
[INFO]
[INFO] Building Unnamed -
com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO]task-segment: [release:perform] (aggregator-style)
[INFO]
[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd
/Users/emiles/Projects/release-workspace/release-parent/target svn
--non-interactive checkout
http://localhost/dev/release-parent/tags/release-parent-0.0.2
/Users/emiles/Projects/release-workspace/release-parent/target/checkout
[INFO] Working directory:
/Users/emiles/Projects/release-workspace/release-parent/target
[INFO] Executing goals 'deploy'...
[WARNING] Base directory is a file. Using base directory as POM location.
[jira] Created: (SCM-505) Linux Synergy client fails to execute scm:update command
Linux Synergy client fails to execute scm:update command Key: SCM-505 URL: http://jira.codehaus.org/browse/SCM-505 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-synergy Affects Versions: 1.2 Environment: Redhat Linux 5 CM/Synergy 7.0 Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530) Java version: 1.6.0_13 Reporter: Subir S Priority: Blocker The linux synergy client using remote client option does not work when using scm:update goal. Error is ccm start -nogui -m -q -n user -pw password cannot find the appropriate database '/cm/dbs/testdb/db' On command line if '-rc' option is used along with ccm start then everything works. Is there something additional to be done to make scm:update goal understand that remote client is in use? If there are some pointers, then i would like to help and send a patch or test it -- 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
[jira] Updated: (SCM-505) Linux Synergy client fails to execute scm:update command
[ http://jira.codehaus.org/browse/SCM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subir S updated SCM-505: Attachment: SCM-505-maven-scm.patch Patch for this issue (created using tortoiseSVN). I dont know what this means. How will you get my changes? I am new to SVN all together. So i have those files already with me, incase this is not sufficient. Do let me know. Linux Synergy client fails to execute scm:update command Key: SCM-505 URL: http://jira.codehaus.org/browse/SCM-505 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-synergy Affects Versions: 1.2 Environment: Redhat Linux 5 CM/Synergy 7.0 Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530) Java version: 1.6.0_13 Reporter: Subir S Priority: Blocker Attachments: SCM-505-maven-scm.patch The linux synergy client using remote client option does not work when using scm:update goal. Error is ccm start -nogui -m -q -n user -pw password cannot find the appropriate database '/cm/dbs/testdb/db' On command line if '-rc' option is used along with ccm start then everything works. Is there something additional to be done to make scm:update goal understand that remote client is in use? If there are some pointers, then i would like to help and send a patch or test it -- 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
[jira] Commented: (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:comment-tabpanelfocusedCommentId=202456#action_202456
]
Subir S commented on SCM-261:
-
This is something very important to fix. Since DCM is always something very
commonly used in CM/Synergy SCM. Will we able to claim Maven-SCM fully supports
CM/Synergy with out resolving this issue.
What help can i extend to get this fixed?
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
[jira] Commented: (SCM-505) Linux Synergy client fails to execute scm:update command
[ http://jira.codehaus.org/browse/SCM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202471#action_202471 ] Subir S commented on SCM-505: - This patch was tested in Windows XP and RHEL 5. CM/Synergy sessions are started in both OSes. Windows starts without -rc option and RHEL with -rc option. Linux Synergy client fails to execute scm:update command Key: SCM-505 URL: http://jira.codehaus.org/browse/SCM-505 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-synergy Affects Versions: 1.2 Environment: Redhat Linux 5 CM/Synergy 7.0 Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530) Java version: 1.6.0_13 Reporter: Subir S Priority: Blocker Attachments: SCM-505-maven-scm.patch The linux synergy client using remote client option does not work when using scm:update goal. Error is ccm start -nogui -m -q -n user -pw password cannot find the appropriate database '/cm/dbs/testdb/db' On command line if '-rc' option is used along with ccm start then everything works. Is there something additional to be done to make scm:update goal understand that remote client is in use? If there are some pointers, then i would like to help and send a patch or test it -- 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
[jira] Commented: (SCM-505) Linux Synergy client fails to execute scm:update command
[ http://jira.codehaus.org/browse/SCM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202641#action_202641 ] Subir S commented on SCM-505: - Thanks! Who would take care of updating also the documentation part. Like adding a note that 'for all ccm start commands for a remote linux/unix client option -rc is also used apart from those already given above' Linux Synergy client fails to execute scm:update command Key: SCM-505 URL: http://jira.codehaus.org/browse/SCM-505 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-synergy Affects Versions: 1.2 Environment: Redhat Linux 5 CM/Synergy 7.0 Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530) Java version: 1.6.0_13 Reporter: Subir S Assignee: Olivier Lamy Priority: Blocker Fix For: 1.3 Attachments: SCM-505-maven-scm.patch The linux synergy client using remote client option does not work when using scm:update goal. Error is ccm start -nogui -m -q -n user -pw password cannot find the appropriate database '/cm/dbs/testdb/db' On command line if '-rc' option is used along with ccm start then everything works. Is there something additional to be done to make scm:update goal understand that remote client is in use? If there are some pointers, then i would like to help and send a patch or test it -- 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
[jira] Updated: (SCM-505) Linux Synergy client fails to execute scm:update command
[ http://jira.codehaus.org/browse/SCM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subir S updated SCM-505: Attachment: SCM-505-maven-scm-formatted.patch Re-submitted patch with correct formatted code. Basically corrected tabs with space replacements, since diff is showing badly indented code. Olivier, can you please update this one. please! Linux Synergy client fails to execute scm:update command Key: SCM-505 URL: http://jira.codehaus.org/browse/SCM-505 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-synergy Affects Versions: 1.2 Environment: Redhat Linux 5 CM/Synergy 7.0 Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530) Java version: 1.6.0_13 Reporter: Subir S Assignee: Olivier Lamy Priority: Blocker Fix For: 1.3 Attachments: SCM-505-maven-scm-formatted.patch, SCM-505-maven-scm.patch The linux synergy client using remote client option does not work when using scm:update goal. Error is ccm start -nogui -m -q -n user -pw password cannot find the appropriate database '/cm/dbs/testdb/db' On command line if '-rc' option is used along with ccm start then everything works. Is there something additional to be done to make scm:update goal understand that remote client is in use? If there are some pointers, then i would like to help and send a patch or test it -- 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
[jira] Commented: (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:comment-tabpanelfocusedCommentId=202647#action_202647
]
Subir S commented on SCM-261:
-
I saw only two references of this kind of hardcoding in source code.
One way to resolve this would be to decifer the database_id by executing this
command. 'ccm dcm -show -dbid'
For DCM enabled databases, this returns the database name configured in DCM
cluster.
For non DCM enabled databases, this returns nothing.
However DCM delimiter is also configurable, and by default it is '#'. But i am
not able to figure out how to know the exact delimiter directly from the
database. Any clues? If this is also found, then we can fix this issue.
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
[jira] Commented: (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:comment-tabpanelfocusedCommentId=202660#action_202660
]
Subir S commented on SCM-261:
-
Ok, there is no way to fetch dcm delimiter from the database using any cli
commands.
Description about it from Telelogic Guide is:
[quote]A DCM Delimiter is the character that is used: 1) Between the database
ID and object instance in object references, 2) Between the database ID and
object version in imported objects that have been checked out in a destination
database, and 3) Between the database ID and task number in some dialogs where
task numbers are displayed.
The default DCM Delimiter is #. The following characters can also be used:
!, ~, or =.
strongThe DCM Delimiter must be the same in all databases in a given DCM
cluster. /strong[unquote]
The line in bold means that this parameter is something which remains same for
all the databases in the distributed cluster. Hence we can take this as a input
parameter in the SCM URL in the end (optional though).
Logic should be: a.) If dbid present, and dcm_delimiter specified, use that to
construct instance. ELSE b.) If dbid present and dcm_delimiter not specified,
use # to construct instance c.) If dbid not present, use '1' as the instance.
Any 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
[jira] Reopened: (SCM-505) Linux Synergy client fails to execute scm:update command
[ http://jira.codehaus.org/browse/SCM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subir S reopened SCM-505: - Reopened since second patch (with formatted code) should be applied. Thanks! Linux Synergy client fails to execute scm:update command Key: SCM-505 URL: http://jira.codehaus.org/browse/SCM-505 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-synergy Affects Versions: 1.2 Environment: Redhat Linux 5 CM/Synergy 7.0 Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530) Java version: 1.6.0_13 Reporter: Subir S Assignee: Olivier Lamy Priority: Blocker Fix For: 1.3 Attachments: SCM-505-maven-scm-formatted.patch, SCM-505-maven-scm.patch The linux synergy client using remote client option does not work when using scm:update goal. Error is ccm start -nogui -m -q -n user -pw password cannot find the appropriate database '/cm/dbs/testdb/db' On command line if '-rc' option is used along with ccm start then everything works. Is there something additional to be done to make scm:update goal understand that remote client is in use? If there are some pointers, then i would like to help and send a patch or test it -- 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
[jira] Commented: (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:comment-tabpanelfocusedCommentId=202995#action_202995
]
Subir S commented on SCM-261:
-
Body Mass,
I guess you are getting confused. An instance is comprised of
database_iddcm_delimiterobjectversion
First thing is:
a.) SCM URL in POM scm element specifies a prep project details.
b.) Consider databases dcmdb1 and dcmdb2 in the SCM cluster. When you check-in
the POM in dcmdb1 with the instance as dcmdb1#1, then it will not work in
dcmdb2. Reason: A prep 'project' is always local to any DCM database. So we
cannot have the configuration which is local to a particular database as part
of the SCM URL. Only global configurations can be put there. Like DCM delimiter
has to be same in every database (both dcmdb1 and dcmdb2), so it can be put to
SCM URL.
c.) We can decifer the database names from db itself.
d.) If you saw the source code, then you would know that on getWorkingProject
and getCompletedTasks use the complete %objectname format in ccm queries.
Secondly what you said is the generic format of objectname in a DCM enabled
database. Atleast i did not understand how that causes a issue here. Incase you
want to elaborate with examples, as to why that makes the current proposed fix
wrong, then that would be great!.
I will try to implement this and see if it works. If it works and
maven-scm-provider-synergy needs a patch i will submit that. If not lets forget
using maven with CM/Synergy.
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
[jira] Created: (SCM-514) Quotes in CommandLine is causing failure to scm:update
Quotes in CommandLine is causing failure to scm:update
--
Key: SCM-514
URL: http://jira.codehaus.org/browse/SCM-514
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-synergy
Affects Versions: 1.3
Environment: Platform OS: RHEL 5
Java: 1.6.0_17
Maven: 2.1.0
Maven SCM: 1.3-SNAPSHOT
SCM: CM/Synergy 7.0
Reporter: Subir S
Priority: Critical
While executing scm:update command in 'Linux', there is a single quote which
appears in the start and end of the argument. This causes the already existing
arguments to have wrong syntax.
mvn scm:update -Dusername=user -Dpassword=pass -X shows the following output:
[DEBUG] STDERR :
[DEBUG] Synergy : Entering getWorkingProject method
[DEBUG] Executing: /bin/sh -c ccm query -u -f %objectname {color:red}
-- additonal start single quote '{color}
owner='user' and status='working' and type='project' and
has_predecessor('sm-3.3:project:inhytest#1')' {color:red}
-- Additional end single quote{color}
[DEBUG] Exit code :1
[DEBUG] STDOUT : unavailable
[DEBUG] STDERR :Warning: Syntax error in query request: owner=user and
status=working and type=project and has_predecessor(sm-3.3:project:inhytest#1)
{color:red}
-- Note that now the single quotes after interpretation by the shell are
removed.{color}
This works fine in 'Windows' platform.
Correct output should be: /bin/sh -c ccm query -u -f %objectname owner='user'
and status='working' and type='project' and
has_predecessor('sm-3.3:project:inhytest#1') {color:red}
--No single quotes, but double quotes and inner single quotes not modified
then.{color}
How to get this working? I have seens some changes to plexus-utils on these
quotes, but could not understand how to workaround this. Please help.
--
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
