Creation of Change set archive from SVN having errors
We are currently in the process of migrating our source control from SVN to RTC.
My workspace is RAD 7.5.4 with RTC client installed from a p2 installer.
In creating a change set archive, I am encountering the following error.
An internal error occurred during: "SVN".
org/tmatesoft/svn/core/io/ISVNEditor.changeDirProperty(Ljava/lang/String;Lorg/tmatesoft/svn/core/SVNPropertyValue;)V
A change set archive has been created (24 revisions before) by another person.
Any ideas? Configuration or environment issues?
Thanks.
My workspace is RAD 7.5.4 with RTC client installed from a p2 installer.
In creating a change set archive, I am encountering the following error.
An internal error occurred during: "SVN".
org/tmatesoft/svn/core/io/ISVNEditor.changeDirProperty(Ljava/lang/String;Lorg/tmatesoft/svn/core/SVNPropertyValue;)V
A change set archive has been created (24 revisions before) by another person.
Any ideas? Configuration or environment issues?
Thanks.
One answer
Karen,
This has been reported as a defect:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=158985
You have two main courses of action you can try
1) Import from an SVN dump file instead. This is the preferred approach and I've seen people have better success w/ dump file rather than the other import.
2) If you must do the current kind of import, per the defect you need to replace your SVNKit plugins to exactly version 1.1.8 (newer versions won't work).
It would not hurt to upgrade to 2.0.0.2 iFix6 before trying either of these approaches. Not sure what version you are currently on but the iFixes have included fixes to SVN import.
This has been reported as a defect:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=158985
You have two main courses of action you can try
1) Import from an SVN dump file instead. This is the preferred approach and I've seen people have better success w/ dump file rather than the other import.
2) If you must do the current kind of import, per the defect you need to replace your SVNKit plugins to exactly version 1.1.8 (newer versions won't work).
It would not hurt to upgrade to 2.0.0.2 iFix6 before trying either of these approaches. Not sure what version you are currently on but the iFixes have included fixes to SVN import.