rtcto / rtc2gitcli Goto Github PK

Hi,

This is a great tool! Thanks for the work you have done here.

I am migrating a fairly big product that contains several streams - several maintenance and one master. Do you have any recommendations for migrating multiple streams?

Please refer the below error. I tired in two versions of scm one is 6.0.6.1 when it didn't work got know in one of the issue solution that repository issue is resolved after downgrading RTC client to 6.0.4 .I can still see the error. Please assist.

C:\Users\E99XXX>scm --version
Build Id: RTC-CLIENT-I20170517-1025
Version: 6.0.4

C:\Users\E99XXX>cd C:\CC_GIT_migration\RTC_GIT_Initlaization

C:\CC_GIT_migration\RTC_GIT_Initlaization>scm load -r https://abubakarmkarajagi:[email protected]/DXXXXXXX/ClearCase.git C:\IBM_RTC_GIT\Target_WS
Password (E9XXX @ https://abubakarmkarajagi:[email protected]/DXXXXXXX/ClearCase.git): ghp_aq1Sh5YbV3srVNVxgeAOZ506noas3S3nO8a
Problem running 'load':
Could not log in to https://abubakarmkarajagi:[email protected]/DXXXXXXX/ClearCase.git as user E9XXX: CRJAZ2382E Cannot connect to the repository at URL "https://abubakarmkarajagi:[email protected]/DXXXXXXX/ClearCase.git". This can happen if you have supplied an incorrect URI or if the server is down. Try logout and re-login with the updated credentials if the password has been changed.
CRJAZ2382E Cannot connect to the repository at URL "https://abubakarmkarajagi:[email protected]/DXXXXXXX/ClearCase.git". This can happen if you have supplied an incorrect URI or if the server is down.
Check the log for details about the error at "C:\Users\E9XXX\AppData\Local\jazz-scm". If you have configured custom logging check your log configuration settings for the path to the log file.

C:\CC_GIT_migration\RTC_GIT_Initlaization>scm load -r https://github.com/XXXXXX/ClearCase.git -u abubakarmkarajagi C:\IBM_RTC_GIT\Target_WS
Password (abubakarmkarajagi @ https://github.com/XXXXXX/ClearCase.git):
Problem running 'load':
Could not log in to https://github.com/XXXXXX/ClearCase.git as user abubakarmkarajagi: CRJAZ2382E Cannot connect to the repository at URL "https://github.com/XXXXXX/ClearCase.git". This can happen if you have supplied an incorrect URI or if the server is down. Try logout and re-login with the updated credentials if the password has been changed.
CRJAZ2382E Cannot connect to the repository at URL "https://github.com/XXXXXX/ClearCase.git". This can happen if you have supplied an incorrect URI or if the server is down.
Check the log for details about the error at "C:\Users\E9XXX\AppData\Local\jazz-scm". If you have configured custom logging check your log configuration settings for the path to the log file.

C:\CC_GIT_migration\RTC_GIT_Initlaization>

while loading the project to eclipse and running got error for plugin.please find error screenshot below.
please help how to fix

It is not clear for me how to prepare the SRC and DST workspaces for the migration. As I run the tool it finds no changeset at all even the stream has a lot.

"TOTAL NUMBER OF CHANGESETS [0]"

In the SRC workspace I set the components to the first baseline and the flow to the stream, in the DST workspace I set the flow to SRC. I tried also with or without the components in the DST but the same result.

Regards,
Istvan

When I execute the scm load command to load the target workspace, I get the following error:

java.lang.IllegalStateException: Found two dtoEvolution elements with the same c
omponentVersion value in bundle com.ibm.team.scm.common.
at com.ibm.team.repository.common.internal.util.ModelElementDescriptor$E
volutionDescriptorComponentVersionComparator.compare(ModelElementDescriptor.java
:223)
at com.ibm.team.repository.common.internal.util.ModelElementDescriptor$E
volutionDescriptorComponentVersionComparator.compare(ModelElementDescriptor.java
:1)
at java.util.TreeMap.compare(TreeMap.java:1188)

Any ideas?

Hi,
I am migrating source code with history from RTC 6.0.4. The history is a bit huge. The migration is not throwing any error but it is not migrating all folders (source code) and all changesets. Has anyone faced such issue? Does it work properly for large projects?

If a project/directory in RTC contains .git folder, it won't be migrated to git.
I occasionally added .git folder when initially shared my project in RTC. Now when I have to migrate it to GIT the migration plug-in leaves the project folder empty.
There should be a way to override the current behaviour since otherwise it's impossible to import that project.

I ran the tool and everything is pretty much fine. But the tool doesn't consider baselines. I read that baselines will be converted to tags, but I see no tags created. Did I miss something?

Problem with scm load -r -u -P <TARGET_WORKSPACE>
uri I have used as clone url -> https://github.com/rtcTo/rtc2gitcli.git
username password i usually used to login to Git.
Target workspace as C:\DevSoftware\Migration\TARGET_WORKSPACE.

But still it shows following error.

C:\DevSoftware\Migration\RTC-scmTools-Win64-6.0.4\jazz\scmtools\eclipse>scm load -r https://github.ibm.com/manjeetdangi/CCBT.git -u manjeetdangi -P ######## C:\DevSoftware\Migration\TARGET_WORKSPACE
Problem running 'load':
Could not log in to https://github.ibm.com/manjeetdangi/CCBT.git as user manjeetdangi: CRJAZ2917E The repository on the following server cannot be reached: https://github.ibm.com/manjeetdangi/CCBT.git. Verify that the server address is correct.Try logout and re-login with the updated credentials if the password has been changed.
CRJAZ2917E The repository on the following server cannot be reached: https://github.ibm.com/manjeetdangi/CCBT.git. Verify that the server address is correct.
Check the log for details about the error at "C:\Users\ManjeetDangi\AppData\Local\jazz-scm". If you have configured custom logging check your log configuration settings for the path to the log file.

I currently use scmtools v5.0.2 for the migration process
Sometimes during migration I encounter issues and errors deriving from scmtools cli,
and I read online that many of these issues are resolved in v6.
However, when trying to run migration with scmtools v6.x it seems not compatible with rtc2gitcli.

Do you have any suggestions / experience with using scmtools v6.x for migration process?

Thanks!
Yael

After migrating many streams from RTC successfully, I encountered an error on a few streams. I noticed this issue because the files in the git folder didnt' match the files in RTC.
After investigating the problem I recognized that after deleting all Files in the current repository and a followed check-in, the plugin can not make another commit after that, but it print out the changesets in the console as normal. I then tried to migrate the files/changes from a different baseline which where checked-in after the problem commit - without any problem. So it seems that after an empty repository the plugin is not able to write new files or commits.

I am trying to migrate changeset history by having two workspaces.

Eg : Source Workspace : 1.0
Target Workspace : 2.0

The code is able to migrate all changesets after 1.0 and in 2.0 but not from start of 1.0.

Help me understand how to that ?

Based on this project is it still working and will the long term support provided with regular updates. Also is there any alternative for the same functionality ? RTC to Git

I see in the logs that the migration is complete for all the Tags but It is not showing the changeset information. The complete migration is not able to find the changesets in the entire process and also the migration shows it took just 0 seconds for each tag that it migrates. Can somebody please advise me on why it is not including/showing me the changeset information in the migration process? Thank you.
I executed the below step:

scm migrate-to-git -r -u -P -m <migration.properties> <SOURCE_WORKSPACE> <TARGET_WORKSPACE>

I'm trying to migrate RTC project stream with multiple components with history starting not from beginning. After accepting first commit, I'm getting several messages about directory checked out from different place and then exception with generic message "load ... before migrate-to-git".

The problem is that for each component accepting its first commit launches 'load' delegate for that component that fails because the component is already loaded. This only works if each component in the "target" workspace has "initial baseline" and thus empty content.

As a workaround, "update" option can be specified.

Hi,
I have set up the migration tool and RTC source/target workspace. I tried to migrate a simple RTC repository as a test but it failed with the following error. What does it mean?

    _Could not initialize data area. Directory is not shared: E:\share_

I am not quite sure how this work to migrate the code to github. Is there somewhere I need to provide the github connection information? does this tool work with private enterprise github server?

Hi ,
My project is not native RTC project, I migrated it in RTC from SVN.
Now I'm migrating my RTC projecct to bitbucket using this tool. This tool did the migration but didn't captured the svn history.
Is there any way I can capture svn history ?

Hi guys,

I get this error:
Subcomando "migrate-to-git" desconhecido

Which means:
subcommand "migrate-to-git" unknow

Do you have any idea of what I am doing wrong? Thanks!

I used scmtools 6.x before. but now am using 5.0.2 and now getting the below error - How can I get rid of this one.

com.ibm.team.rtc.cli.infrastructure.internal.core.ISubcommandDefinition$LoadOptionsException: org.eclipse.core.runtime.CoreException: Plug-in to.rtc.cli.migrate was unable to load class to.rtc.cli.migrate.git.MigrateToGitOptions.
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandDefinition.getOptions(SubcommandDefinition.java:107)
at com.ibm.team.rtc.cli.infrastructure.internal.subcommands.HelpCmd.showSubcommand(HelpCmd.java:280)
at com.ibm.team.rtc.cli.infrastructure.internal.subcommands.HelpCmd.showSubCommand(HelpCmd.java:243)
at com.ibm.team.rtc.cli.infrastructure.internal.subcommands.HelpCmd.run(HelpCmd.java:112)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: org.eclipse.core.runtime.CoreException: Plug-in to.rtc.cli.migrate was unable to load class to.rtc.cli.migrate.git.MigrateToGitOptions.
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:904)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandDefinition.getOptions(SubcommandDefinition.java:105)

This is working just fine if you dont want to change the order of the git commit message components: rtc workitem number -> rtc commit message -> rtc workitem summary as mentioned here #32

In my opion the argument index $ should be used instead so that the the actual index of the method parameters at String.format() are getting addressed rather than their bare order. So %1$s %2$s %3$s will give the same result as before but now it is possible to customize the commit message even more by doing something like that: %3$s %2$s, which will print the rtc workitem summary in front of the rtc commit message and completly skip the rtc workitem number.

In addition to that i would also add a documentation for the %3$s parameter added in #34

I am going to create a merge request if a get positive feedback to my recommandation.

Hi, I used all the steps and it is successful. One thing I observe is if the rtc changes are promoted agianst a workitem, the git history shows as "No Comment". I expected it to be workitem number and description that the rtc changes are promted to. can someone tell me if this workitem reference is stored in git somewhere. if so where and how can i push the same to git. This is very helpful as everything else works fine. Appreciate your help. Thanks/

The log somewhat looks like this -
[2018-04-30 14:35:25] Migrated [HEAD] [334]/[335] changesets. Accept took 1933ms commit took 69ms
[2018-04-30 14:35:28] Accepting changes:
[2018-04-30 14:35:29] Repository: https://jazzcxxxx.hursley.ibm.com:9443/ccm/
[2018-04-30 14:35:29] Workspace: (6706) "FO2-dst"
[2018-04-30 14:35:29] Component: (5940) "Foundation_Others"
[2018-04-30 14:35:29] Change sets:
[2018-04-30 14:35:29] (6694) ----$ xxxxxx "" 13-Nov-2017 06:14 PM
[2018-04-30 14:35:29] Changes:
[2018-04-30 14:35:29] ---c- /Foundation_Others/RMG_Scripts/FoundationCD.pl
[2018-04-30 14:35:29] Work items:
[2018-04-30 14:35:29] (6691) 550545 "FP image build process has to be enhanced to handle syste..."
[2018-04-30 14:35:29] Accept command completed successfully.
[2018-04-30 14:35:29] DelegateCommand [accept FO2-dst _7v7EcMhnEeemv-_JpSZ3Mg baseline[false]] finished in

I have tried the plugin on windows and it works just fine. However we are running into issues with few folders checked in in RTC through the browser where there is trailing white space in folder names. Would like to try the plugin on linux platform to see if the changesets associated with these folder names get accepted successfully.

I have installed eclipse and configured SCM Path in my linux server. The plugin is copied under /jazz/scmtools/eclipse/plugins . However the migrate-to-git command is not enabled. Any suggestions would be helpful.

Hi,

I have used the migration command as below.

scm migrate-to-git -r -u -P -m <migration.properties> <SOURCE_WORKSPACE> <TARGET_WORKSPACE>

The command is executing successfully now with no error, however, it is not showing any baselines or changesets. We have multiple changesets and baselines.

Things I have done.

Before using this command, I have created a source workspace and target workspace.

after this I have loaded initial target workspace with below command.

scm load -r -u -P <TARGET_WORKSPACE>

Attaching the screen shot of actual migration.

I had run migration command twice.

1. In first attempt, below line is commented in "migration.properties"
   #rtc.baseline.include=^(.*)$

2. I re run the command with the below line not commented in second attempt.
   rtc.baseline.include=^(.*)$

Attaching final folder structure screen shot.

In this folder I can not see any code or projects or components. So the command is not showing any error but don't know if migration was successful.

am I missing any steps ?

I perfromed migration succesfully for couple of project however for some of my project from RTC to Bitbucket, we observed some descripencies.

1 .zip file migrated from RTC to BB but no RTC history migrated to Bitbucket
2, .xlsx file migrated but has more history in BB than RTC

Is above are limitations of this tool ?

I have successfully cloned and compiled the project. I can even run it from within the eclipse. But when i try to use it from the command line I fail. Actually I tried to put the jar file exported from eclipse to the plugins folder but the sub command migrate-to-git is still unknown. The generated jar contains the META-INF file from the src folder. What else should I do?

Regards,
Istvan

Hello,

when I try to run the command migrate-to-git, I get the following exceptions:

Create the list of baselines
java.lang.NullPointerException
at to.rtc.cli.migrate.MigrateTo.createTagListFromBaselines(MigrateTo.java:251)
at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:117)
at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

Can someone help me?

Thank you,
Giulia

In commit history complete commit message not present in git history .

I tried to modify parameter(commit.message.format) in migration.properties file but could not able to get exact commit message .Could you please provide details how to keep commit message.format value to get complete RTC history commit message to git commit comment .

Example:
RTC history commit message:
123:Test message- change on 20200101

Git history commit message :
123 change on 20200101

So message is trimmed and displayed in git comment .in above example Test message is missing ,content between : and - symbol

Hi All, while running the command from rtc2git, we are getting issues ‘Problem running accept’ change wasn’t successfully accepted in workspace.

Can someone help with this please? We are stuck and cant move forward

Hello again,
I have to use certificate login to RTC but plugin seams not to support it. So I added code which I thought should enable it. Branch: certificate-login
But then I run I get exception:
Internal error at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:721) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130) at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:76) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:607) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408) at org.eclipse.equinox.launcher.Main.main(Main.java:1384) Caused by: java.lang.RuntimeException: java.lang.RuntimeException: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:175) at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51) ... 17 more Caused by: java.lang.RuntimeException: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:168) ... 19 more Caused by: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:721) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53) at to.rtc.cli.migrate.command.RtcCommandDelegate.run(RtcCommandDelegate.java:40) at to.rtc.cli.migrate.command.AcceptCommandDelegate.run(AcceptCommandDelegate.java:33) at to.rtc.cli.migrate.RtcMigrator.acceptAndLoadChangeSet(RtcMigrator.java:114) at to.rtc.cli.migrate.RtcMigrator.accept(RtcMigrator.java:95) at to.rtc.cli.migrate.RtcMigrator.migrateTag(RtcMigrator.java:50) at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:164) ... 19 more Caused by: java.lang.NullPointerException at com.ibm.team.filesystem.cli.core.util.RepoUtil.login(RepoUtil.java:648) at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAnc(RepoUtil.java:459) at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAncestor(RepoUtil.java:561) at com.ibm.team.filesystem.cli.client.internal.subcommands.AcceptCmd.generateAcceptParms(AcceptCmd.java:560) at com.ibm.team.filesystem.cli.client.internal.subcommands.AcceptCmd.run(AcceptCmd.java:143) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51) ... 25 more

I looked inside RepoUtil.login() class and it appears to still try to get username and equal it:
if(repoDTO != null && repoDTO.getContributorItemIdLoggedInContributor() != null) { if(info.getUsername().equals(repoDTO.getUserId())) {

Can you help with this? How to get certificate login support?

Regards
Modestas

I am unable to compile. I get a lot of unresolved dependecies. Attaching
log.txt

Hello,

My Org has decided to migrate code from RTC Jazz to Bitbucket so I chose this utility to migrate code with commit/changesets history.

But while migrating code, I found that one folder named "exception" containing 4 .java files skipped rest everything is migrated successfully.

In further Investigation, I monitor all the logs and migration process then found that earlier folder name was "Exception" with same set of files. Till here I can see that folder was present with all files but as soon as folder name modified from "Exception" to "exception" under on of commit/changeset it gets deleted from final/Target folder.

Is there any specific reason for this ? Is this expected behavior ? or code change is required for this.
Any suggestions or help are most welcome.

I suspect the migration fails because of a symbolic link problem (on Windows machine) - when the RTC repository contains directory/file links.

Is there a solution for this scenario?

Thanks!

Hi,

On importing the "rtc2gitcli" project in eclipse getting below error. How do we resolve it ?

The Eclipse Requirements section of the readme implies some steps to import this tool into my Jazz SCM tools, but doesn't spell them out. Can someone be a little more specific about how to install rtc2gitcli into my Eclipse/jazz scm setup? Thanks!

Hello All,

Using rtc2gitcli, I was trying to migrate our rtc code to git repo.
but facing RuntimeException, also few java packages are not resolved.

configured RTC client 5.0.2 , created source and Target repository(initial baseline)
using jdk 1.8
eclipse photon
rtc2gitcli-master to migrate the code

but was facing multiple issues.
attached log, please help on priority
.log

Does this project support migration of large amounts of changesets, and large sizes of changesets? (we have changesets that contain hundreds of files)

Can I somehow fine-tune this process and improve running time? maybe by changing migration.properties parameters?

I followed all the steps in rtc2gitcli and started migration. I get the following error - Can anyone help me with this. Do we need to create git repo before and do some other settings? I dont see any reference to git repo in this document. It would be good if we mention those steps here.

ccuRev Transaction Id: 50 with comment: L10N Kit Version Controlling
[2018-04-18 10:26:47] Baseline [HEAD] with original name [HEAD] created at [Sun Aug 17 12:42:55 IST 292278994] total number of changesets [0] will be tagged [false]
[2018-04-18 10:26:47] TOTAL NUMBER OF CHANGESETS [144]
[2018-04-18 10:26:47] ********** BASELINE INFOS **********
[2018-04-18 10:26:47] Start migration of tags.
[2018-04-18 10:26:48] org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of add command
at org.eclipse.jgit.api.AddCommand.call(AddCommand.java:246)
at to.rtc.cli.migrate.git.GitMigrator.gitCommit(GitMigrator.java:228)
at to.rtc.cli.migrate.git.GitMigrator.init(GitMigrator.java:435)
at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:147)
at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
Caused by: java.io.IOException: The process cannot access the file because another process has locked a portion of the file
at java.io.FileInputStream.read0(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at org.eclipse.jgit.util.IO.readWholeStream(IO.java:216)
at org.eclipse.jgit.treewalk.WorkingTreeIterator.possiblyFilteredInputStream(WorkingTreeIterator.java:384)
at org.eclipse.jgit.treewalk.WorkingTreeIterator.getEntryContentLength(WorkingTreeIterator.java:559)
at org.eclipse.jgit.api.AddCommand.call(AddCommand.java:226)
... 21 more
Migration took [19] s

The GIT commit message is generated basing on RTC Wi # and change set comment. If change set comment is empty, commit message would consist only of WI # what is not very convenient. Also as RTC includes WI summary to the change set representation in e.g. Eclipse client, people tend to keep comments empty.

I'd suggest more possibilities to customize commit message, e.g. using first WI summary as commit message text. Also it would be good to have message basing on WI texts, not only numbers.

I'm running into 2 folder or file issues when attempting to run the scm migrate-to-git as a plugin.

1) If I attempt to run the script from a regular (empty) folder i.e "C:\test" I get the following error:
RuntimeException: "C:\test" is not shared. null at ...

Full stack trace:
!ENTRY org.eclipse.osgi 4 0 2019-11-22 06:41:45.715
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: com.ibm.team.filesystem.cli.core.util.CLIFileSystemClientException: Status ERROR: com.ibm.team.filesystem.cli.core code=30 "c:\test" is not shared. null
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:143)
at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
Caused by: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: com.ibm.team.filesystem.cli.core.util.CLIFileSystemClientException: Status ERROR: com.ibm.team.filesystem.cli.core code=30 "c:\test" is not shared. null
at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:731)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
... 13 more
Caused by: java.lang.RuntimeException: com.ibm.team.filesystem.cli.core.util.CLIFileSystemClientException: Status ERROR: com.ibm.team.filesystem.cli.core code=30 "c:\test" is not shared. null
at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:180)
at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
... 16 more
Caused by: com.ibm.team.filesystem.cli.core.util.CLIFileSystemClientException: Status ERROR: com.ibm.team.filesystem.cli.core code=30 "c:\test" is not shared. null
at com.ibm.team.filesystem.cli.core.util.StatusHelper.createException(StatusHelper.java:403)
at com.ibm.team.filesystem.cli.core.util.StatusHelper.inappropriateArgument(StatusHelper.java:486)
at com.ibm.team.filesystem.cli.core.util.RepoUtil.getSandboxPathsAndRegister(RepoUtil.java:1289)
at com.ibm.team.filesystem.cli.core.util.RepoUtil.getSharesInSandbox(RepoUtil.java:1315)
at com.ibm.team.filesystem.cli.core.util.RepoUtil.getComponentsInSandbox(RepoUtil.java:1355)
at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:149)
... 18 more

2) If, however, I attempt to run the command from the SCM tools folder ("C:\Tools\jazz\scmtools\eclipse") I get a different error:
JGitInternalException / IO Exception: The process cannot access the file because another process has locked a portion of the file.

Full stack trace:
!ENTRY org.eclipse.osgi 4 0 2019-11-22 06:46:13.027
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of add command
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:143)
at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
Caused by: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of add command
at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:731)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
... 13 more
Caused by: java.lang.RuntimeException: org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of add command
at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:180)
at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
... 16 more
Caused by: org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of add command
at org.eclipse.jgit.api.AddCommand.call(AddCommand.java:246)
at to.rtc.cli.migrate.git.GitMigrator.gitCommit(GitMigrator.java:228)
at to.rtc.cli.migrate.git.GitMigrator.init(GitMigrator.java:435)
at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:147)
... 18 more

Any thoughts that might help me overcome these errors? My RTC repository is v5.0.2.

Hello,

I ran the steps mentioned at https://github.com/rtcTo/rtc2gitcli/wiki/Setup but I get the following error while running the launch configuration rtc2git

Error:
Problem running 'help':
Unknown subcommand "migrate-to-git". Try 'scm help' for more information.

Any pointers for me to proceed?

Hi,

I am using the docker image with scm 5.0.2 to migrate some of our components.
I ran into the following exception during the migration of a specific component.

[2022-01-31 13:50:47] Initialize RTC connection with connection timeout of 900s [2022-01-31 13:50:50] Get full history information from RTC. This could take a large amount of time. [2022-01-31 13:50:50] Create the list of baselines [2022-01-31 13:50:51] java.lang.NullPointerException at to.rtc.cli.migrate.MigrateTo.createTagListFromBaselines(MigrateTo.java:251) at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:117) at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130) at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408) at org.eclipse.equinox.launcher.Main.main(Main.java:1384) Migration took [3] s Unexpected exception com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: java.lang.NullPointerException at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:731) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130) at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408) at org.eclipse.equinox.launcher.Main.main(Main.java:1384) Caused by: java.lang.RuntimeException: java.lang.NullPointerException at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:180) at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51) ... 17 more Caused by: java.lang.NullPointerException at to.rtc.cli.migrate.MigrateTo.createTagListFromBaselines(MigrateTo.java:251) at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:117) ... 19 more Scm: An error has occurred. See the log file /var/data/dev/.metadata/.log.

From what I gather from the code the Baseline Entry doesn't actually have a baseline. Does that mean the entry is empty and can be skipped or is that a bug in scm or rtc respectively?

Thank you in advance for your help.

Currently we are trying to migrate multiple streams with one single component across all these streams set at different baselines.

Can anyone suggest how can this be achieved using this tool?

Hello there,

we are going to use this tool for migrating some RTC 6.0.2 projects, but we can't build the rt2gitcli project due to problems with Eclipse/RTC Client build process. Is there a possibility of getting the binaries for (all) rtc2git repos?

Regards,

Raynor83

I'm running migrate-to-git but getting error -
JGitInternalException - Exception caught during execution of add command

PFA for detailed error log

HI I am new to git&bitbucket & tasked to migrate to RTC project to bitbucket. I have set the target directory & SCMCLI(RTC6.0.4) & the eclipse maven project successfully( i can list migrate-to-git in SCM help) but not sure where to update the git repository (link/users) details? can anybody assist please.

Hi, I tried to migrate with the baseline tagged.

So I update the migration.properties to uncomment this line.
rtc.baseline.include=^(.*)$
and begin to the migration.

I had run into this error. Could you please help me how to resolve it? I cannot be sure why it says the tag already exists.
thanks

=====================================================
tag Initial_Baseline_20120405-182919
tagger PersonIdent[RTC 2 git, [email protected], Mon Apr 16 11:23:36 2018 +0800]

}' already exists
at org.eclipse.jgit.api.TagCommand.updateTagRef(TagCommand.java:193)
at org.eclipse.jgit.api.TagCommand.call(TagCommand.java:164)
at to.rtc.cli.migrate.git.GitMigrator.createTag(GitMigrator.java:481)
... 21 more
Migration took [13] s
Unexpected exception
com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: java.lang.RuntimeException: Unable to tag
at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:731)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Unable to tag
at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:180)
at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
... 17 more
Caused by: java.lang.RuntimeException: Unable to tag
at to.rtc.cli.migrate.git.GitMigrator.createTag(GitMigrator.java:485)
at to.rtc.cli.migrate.RtcMigrator.migrateTag(RtcMigrator.java:75)
at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:169)
... 19 more
Caused by: org.eclipse.jgit.api.errors.RefAlreadyExistsException: tag 'Tag={
object ce8910fdca219b92dd55b204e7e2fcec1be6bbd3
type commit
tag Initial_Baseline_20120405-182919
tagger PersonIdent[RTC 2 git, [email protected], Mon Apr 16 11:23:36 2018 +0800]

}' already exists
at org.eclipse.jgit.api.TagCommand.updateTagRef(TagCommand.java:193)
at org.eclipse.jgit.api.TagCommand.call(TagCommand.java:164)
at to.rtc.cli.migrate.git.GitMigrator.createTag(GitMigrator.java:481)
... 21 more

If the change set contains a move of a folder in the root of the sandbox under another folder it fails the following way
[2017-06-27 14:27:13] com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Cannot move share from /00_Documents to /0Archive_Inception/00_Documents because destination conflicts with existing share /0archive_inception at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:731) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53) at to.rtc.cli.migrate.command.RtcCommandDelegate.run(RtcCommandDelegate.java:35) at to.rtc.cli.migrate.command.AcceptCommandDelegate.run(AcceptCommandDelegate.java:33) at to.rtc.cli.migrate.RtcMigrator.acceptAndLoadChangeSet(RtcMigrator.java:114) at to.rtc.cli.migrate.RtcMigrator.accept(RtcMigrator.java:95) at to.rtc.cli.migrate.RtcMigrator.migrateTag(RtcMigrator.java:50) at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:164) at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130) at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408) at org.eclipse.equinox.launcher.Main.main(Main.java:1384) Caused by: java.lang.IllegalArgumentException: Cannot move share from /00_Documents to /0Archive_Inception/00_Documents because destination conflicts with existing share /0archive_inception at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore$1.locking(CopyFileAreaStore.java:1426) at com.ibm.team.filesystem.client.internal.copyfileareas.BatchingLock.acquire(BatchingLock.java:362) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore.beginBatchingWithLock(CopyFileAreaStore.java:2309) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore.moveSharingInfo(CopyFileAreaStore.java:1416) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileArea.moveInfo(CopyFileArea.java:342) at com.ibm.team.filesystem.client.internal.load.UpdateMutator.updateMetaDataAfterMove(UpdateMutator.java:3310) at com.ibm.team.filesystem.client.internal.load.UpdateMutator.move(UpdateMutator.java:1900) at com.ibm.team.filesystem.client.internal.load.UpdateMutator.moveSubtree(UpdateMutator.java:1853) at com.ibm.team.filesystem.client.internal.load.UpdateMutator.execute(UpdateMutator.java:2179) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:90) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation.loadFileArea(UpdateOperation.java:450) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation.updateCopyFileArea(UpdateOperation.java:316) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation.access$0(UpdateOperation.java:276) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation$1.run(UpdateOperation.java:246) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager$1.run(ResourceSharingManager.java:77) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager.runWithinFileSystemLock(ResourceSharingManager.java:89) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:165) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:145) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation.execute(UpdateOperation.java:268) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:90) at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.doAccept(WorkspaceUpdateOperation.java:916) at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.access$0(WorkspaceUpdateOperation.java:837) at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation$1.run(WorkspaceUpdateOperation.java:741) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager$1.run(ResourceSharingManager.java:77) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager.runWithinFileSystemLock(ResourceSharingManager.java:89) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:165) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:145) at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.execute(WorkspaceUpdateOperation.java:753) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:90) at com.ibm.team.filesystem.client.internal.rest.util.WorkspaceUpdateUtil.workspaceUpdate(WorkspaceUpdateUtil.java:123) at com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.postWorkspaceUpdate(FilesystemRestClient.java:859) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.ibm.team.filesystem.client.daemon.JSONHandler.handle(JSONHandler.java:322) at com.ibm.team.filesystem.client.internal.http.HttpConnection.readNextRequest(HttpConnection.java:628) at com.ibm.team.filesystem.client.internal.http.HttpConnection$1.run(HttpConnection.java:470) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:364) at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeErrorObj(JSONDeserializer.java:957) at com.ibm.team.filesystem.client.internal.marshalling.ExceptionHandlingJSONDeserializer.deserializeErrorObj(ExceptionHandlingJSONDeserializer.java:128) at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeException(JSONDeserializer.java:933) at com.ibm.team.filesystem.client.internal.marshalling.EObjectJSONDeserializer.deserializeError(EObjectJSONDeserializer.java:71) at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeRequest(RestInvocationHandler.java:267) at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeAndReturnResult(RestInvocationHandler.java:221) at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invokeInternal(RestInvocationHandler.java:368) at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invoke(RestInvocationHandler.java:311) at com.sun.proxy.$Proxy0.postWorkspaceUpdate(Unknown Source) at com.ibm.team.filesystem.cli.client.internal.subcommands.AcceptCmd.run(AcceptCmd.java:152) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51) ... 25 more java.lang.RuntimeException: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Cannot move share from /00_Documents to /0Archive_Inception/00_Documents because destination conflicts with existing share /0archive_inception at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:168) at to.rtc.cli.migrate.git.MigrateToGit.run(MigrateToGit.java:25) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370) at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130) at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408) at org.eclipse.equinox.launcher.Main.main(Main.java:1384) Caused by: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Cannot move share from /00_Documents to /0Archive_Inception/00_Documents because destination conflicts with existing share /0archive_inception at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:731) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53) at to.rtc.cli.migrate.command.RtcCommandDelegate.run(RtcCommandDelegate.java:35) at to.rtc.cli.migrate.command.AcceptCommandDelegate.run(AcceptCommandDelegate.java:33) at to.rtc.cli.migrate.RtcMigrator.acceptAndLoadChangeSet(RtcMigrator.java:114) at to.rtc.cli.migrate.RtcMigrator.accept(RtcMigrator.java:95) at to.rtc.cli.migrate.RtcMigrator.migrateTag(RtcMigrator.java:50) at to.rtc.cli.migrate.MigrateTo.run(MigrateTo.java:164) ... 19 more Caused by: java.lang.IllegalArgumentException: Cannot move share from /00_Documents to /0Archive_Inception/00_Documents because destination conflicts with existing share /0archive_inception at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore$1.locking(CopyFileAreaStore.java:1426) at com.ibm.team.filesystem.client.internal.copyfileareas.BatchingLock.acquire(BatchingLock.java:362) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore.beginBatchingWithLock(CopyFileAreaStore.java:2309) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore.moveSharingInfo(CopyFileAreaStore.java:1416) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileArea.moveInfo(CopyFileArea.java:342) at com.ibm.team.filesystem.client.internal.load.UpdateMutator.updateMetaDataAfterMove(UpdateMutator.java:3310) at com.ibm.team.filesystem.client.internal.load.UpdateMutator.move(UpdateMutator.java:1900) at com.ibm.team.filesystem.client.internal.load.UpdateMutator.moveSubtree(UpdateMutator.java:1853) at com.ibm.team.filesystem.client.internal.load.UpdateMutator.execute(UpdateMutator.java:2179) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:90) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation.loadFileArea(UpdateOperation.java:450) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation.updateCopyFileArea(UpdateOperation.java:316) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation.access$0(UpdateOperation.java:276) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation$1.run(UpdateOperation.java:246) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager$1.run(ResourceSharingManager.java:77) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager.runWithinFileSystemLock(ResourceSharingManager.java:89) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:165) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:145) at com.ibm.team.filesystem.client.internal.operations.UpdateOperation.execute(UpdateOperation.java:268) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:90) at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.doAccept(WorkspaceUpdateOperation.java:916) at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.access$0(WorkspaceUpdateOperation.java:837) at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation$1.run(WorkspaceUpdateOperation.java:741) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager$1.run(ResourceSharingManager.java:77) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager.runWithinFileSystemLock(ResourceSharingManager.java:89) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:165) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:145) at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.execute(WorkspaceUpdateOperation.java:753) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:90) at com.ibm.team.filesystem.client.internal.rest.util.WorkspaceUpdateUtil.workspaceUpdate(WorkspaceUpdateUtil.java:123) at com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.postWorkspaceUpdate(FilesystemRestClient.java:859) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.ibm.team.filesystem.client.daemon.JSONHandler.handle(JSONHandler.java:322) at com.ibm.team.filesystem.client.internal.http.HttpConnection.readNextRequest(HttpConnection.java:628) at com.ibm.team.filesystem.client.internal.http.HttpConnection$1.run(HttpConnection.java:470) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:364) at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeErrorObj(JSONDeserializer.java:957) at com.ibm.team.filesystem.client.internal.marshalling.ExceptionHandlingJSONDeserializer.deserializeErrorObj(ExceptionHandlingJSONDeserializer.java:128) at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeException(JSONDeserializer.java:933) at com.ibm.team.filesystem.client.internal.marshalling.EObjectJSONDeserializer.deserializeError(EObjectJSONDeserializer.java:71) at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeRequest(RestInvocationHandler.java:267) at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeAndReturnResult(RestInvocationHandler.java:221) at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invokeInternal(RestInvocationHandler.java:368) at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invoke(RestInvocationHandler.java:311) at com.sun.proxy.$Proxy0.postWorkspaceUpdate(Unknown Source) at com.ibm.team.filesystem.cli.client.internal.subcommands.AcceptCmd.run(AcceptCmd.java:152) at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51) ... 25 more

My temporary workaround is to delete all but .git, load again, delete all but .git .jazz5 .metadata and run again. In this way it adds a new inital commit an miss the failed commit but continues. I also patched it not create inital commit in case the .git already exists but still missing one commit that failed. Actually the changes are commited with the next commit.

Regards,
Istvan

I tried cloning the project and also downloading the project. Neither of them gave me the hamcrest jar file. I want to set break points and debug the code to learn how it works. Right now, I am facing failure with NoClassDefFoundError for the org.hamcrest class. I manually added the library and still getting the error. Could you please let me know what should be done to get the project loaded to eclipse properly and debug hassle free?

Have attached a couple of screenshots for your reference:

Hello,
I was exploring this tool and got this error while trying to migrate:

Unexpected exception com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: com.ibm.team.filesystem.cli.core.util.CLIFileSystemClientException: Status ERROR: com.ibm.team.filesystem.cli.core code=2 Could not log in to https://url/: Your client is version 5.0.1, and the server is version 5.0. These versions are not compatible. Your client is version 5.0.1, and the server is version 5.0. These versions are not compatible. Check the log for details about the error at "C:\Users\user\AppData\Local\jazz-scm". If you have configured custom logging check your log configuration settings for the path to the log file. null

Is there plugin versions for client 5.0?