Upon having a change that causes accetp to throw java.lang.IllegalArgumentException due to bad chars in a folder name, how do we get past this so that accept works again?
one of our users fell into the trap that the Web Client sets regarding renaming folders: he accidentally put / chars in the name, thinking that would move the folder. The webclient cheerfully accepted the / chars, and, delivered the change immediately.
The user then reverted the change.
no matter.
All attempts to accept these changes fail with the exception mentioned above.
We are using RTC 4.0.3 on our server.
Thoughts?
The user then reverted the change.
no matter.
All attempts to accept these changes fail with the exception mentioned above.
We are using RTC 4.0.3 on our server.
Thoughts?
2 answers
One comment - one workaround I have been able to apply to a CI build workspace-repository, but may not help developers with pending changes they haven't delivered...:
Recreate the workspace-repository, to "jump over" the nasty accept:
Recreate the workspace-repository, to "jump over" the nasty accept:
- create a snapshot on the latest change that reverted the nasty bad chars
- derive a new workspace-repository from that snapshot
Further comment -
After I created the snapshot, as mentioned in my previous post, users who were getting the exception upon Accept, now were able to move forward.
I had also re-created a workspace repository, as mentioned in my previous post, though I doubt *that* had anything to do with it for other users.
I don't have a theory of operation to suggest. But wanted to post the facts nevertheless.
Cheers...
After I created the snapshot, as mentioned in my previous post, users who were getting the exception upon Accept, now were able to move forward.
I had also re-created a workspace repository, as mentioned in my previous post, though I doubt *that* had anything to do with it for other users.
I don't have a theory of operation to suggest. But wanted to post the facts nevertheless.
Cheers...