Check-in trouble
A customer is running into an issue when checking in .jar files. Occasionally, when a checkin is attempted the following error message occurs:
"Check-in" has encountered a problem. In Details: Checking-in changes to new change set The initial check-in works, but after that, when the file is replaced by a newer version outside of the RTC client and after RTC detects that the file has changed (in the Pending Changes view), the check-in fails with this message. A similar issue is described in http://jazz.net/forums/viewtopic.php?p=40255 But the workaround suggested there (reloading workspace) is too cumbersome as it happens regularly. Any ideas what could be causing this and if/how we can fix or work around this? Environment: RTC 2.0.0.2 iFix4 on Redhat with WAS and Oracle. The RTC client is running on Windows. |
2 answers
Thanks Christophe!
Now that I know what is going on, I am able to reproduce the customers' problem as well. Being slightly impatient and not wanting to wait until Eclipse picks up the file change, I developed a habit of doing a manual Refresh of a file that is modified outside Eclipse. So, I never saw the problem myself. So with RTC 2.0.0.2 you have two options: either refresh the file/project before checkin or enable the preference setting |
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.