Error in MKS plugin

I am currently evaluating a newer version of MKS (we intend to switch to MKS 2007), and I am also looking at the integration into IDEA.
However, when attempting to invoke the "Show History" action, I get an error message with the following stack trace:

com.intellij.openapi.vcs.VcsException: unknown date format for 18.02.2004 12:52:46 (expected ). This may be an encoding issue, encoding used was IBM437
at org.intellij.vcs.mks.sicommands.ViewMemberHistoryCommand.parseDate(
at org.intellij.vcs.mks.sicommands.ViewMemberHistoryCommand.execute(
at org.intellij.vcs.mks.history.MksVcsHistoryProvider.getRevisions(
at org.intellij.vcs.mks.history.MksVcsHistoryProvider.access$000(
at org.intellij.vcs.mks.history.MksVcsHistoryProvider$1.getRevisionList(
at com.intellij.openapi.vcs.impl.AbstractVcsHelperImpl.showFileHistory(
at com.intellij.openapi.vcs.actions.TabbedShowHistoryAction.actionPerformed(
at com.intellij.openapi.vcs.actions.AbstractVcsAction.actionPerformed(
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.a(
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.b(
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.dispatchKeyEvent(
at com.intellij.ide.IdeEventQueue.b(
at com.intellij.ide.IdeEventQueue.dispatchEvent(
at java.awt.EventDispatchThread.pumpOneEventForFilters(
at java.awt.EventDispatchThread.pumpEventsForFilter(
at java.awt.EventDispatchThread.pumpEventsForHierarchy(
at java.awt.EventDispatchThread.pumpEvents(
at java.awt.EventDispatchThread.pumpEvents(

Is there a workaround to prevent this?

Thanks in advance and best regards,

Comment actions Permalink

Hi Jens,

This issue should is partially corrected in 0.7.1 (I guess you're using this version ?).

You should go to the MKS VCS configuration (Settings> VersionCOntrol> MKS) and change the date format there, to able to parse dates outputted by the si viewhistory command.
I had to do this, as this format seems to change based on locales, or MKS server configuration, and I don't know a way to know beforehand which one should be used.
In your case, MM.dd.yyyy hh:mm:ss should be appropriate.

The remaining bug in 0.7.1 is that this setting is not persisted, I'll publish 0.7.2 later today hopefully with a fix for this one.


Comment actions Permalink

the new version (0.7.2) has just been released


Please sign in to leave a comment.