Vault Eclipse Plugin 4.0.6 on Windows 7 x64

[koye]

I am using the Vault Eclipse Plugin (4.0.6.15954) and am experiencing some problems with basic checkout / checkin commands. If I am reading the output correctly, the plugin seems to be acting as if it is on a UN*X system (see stack trace below). Do I have to do something to indicate my system type? I tried to hack around this by installing Cygwin (to add 'chmod') and this allowed me to check out. When I attempt to check files in, however, I get an "Operation in progress" dialog but the plugin does not display any items to check in.

Any help would be greatly appreciated.

-Kris
Eclipse 3.5.2 (64bit)
Windows 7 Professional (64bit)
Vault Plugin 4.0.6 (Build 15954)

Local file update for $/Ekaria/App/OrderInjection3/src/com/ekaria/Top.java failed: java.lang.RuntimeException: Error executing external command: "chmod" "+w" "C:\Vault\Ekaria\App\OrderInection3\src\com\ekaria\Top.java" ---> java.io.IOException: Cannot run program "chmod": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
at java.lang.Runtime.exec(Runtime.java:593)
at com.sg.util.process.ProcessRunner.run(ProcessRunner.java:419)
at com.sg.jni.UnixFallbackBase.exec(UnixFallbackBase.java:44)
at com.sg.jni.filesystem.UnixFallbackFileSystem.setReadOnly(UnixFallbackFileSystem.java:70)
at VaultLib.Misc.SetFileAttributes(Unknown Source)
at VaultClientOperationsLib.WorkingFolder.MakeWritable(Unknown Source)
at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(Unknown Source)
at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(Unknown Source)
at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(Unknown Source)
at VaultClientOperationsLib.ClientInstance.Get(Unknown Source)
at VaultClientOperationsLib.ClientInstance.Get(Unknown Source)
at VaultClientIntegrationLib.ServerOperations.ProcessCommandCheckout(ServerOperations.cs:338)
at com.sourcegear.vault.ui.commands.CheckOutCommand.work(CheckOutCommand.java:22)
at com.sourcegear.vault.ui.commands.AbstractCommand.run(AbstractCommand.java:89)
at com.sourcegear.vault.ui.commands.AbstractCommand.run(AbstractCommand.java:219)
at com.sg.uihelper.runnable.DeferredProgressMonitorDialogContext$RunnableWithProgressWrapper.run(DeferredProgressMonitorDialogContext.java:173)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--- End of inner exception stack trace ---
at com.sg.jni.UnixFallbackBase.exec(UnixFallbackBase.java:47)
at com.sg.jni.filesystem.UnixFallbackFileSystem.setReadOnly(UnixFallbackFileSystem.java:70)
at VaultLib.Misc.SetFileAttributes(Unknown Source)
at VaultClientOperationsLib.WorkingFolder.MakeWritable(Unknown Source)
at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(Unknown Source)
at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(Unknown Source)
at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(Unknown Source)
at VaultClientOperationsLib.ClientInstance.Get(Unknown Source)
at VaultClientOperationsLib.ClientInstance.Get(Unknown Source)
at VaultClientIntegrationLib.ServerOperations.ProcessCommandCheckout(ServerOperations.cs:338)
at com.sourcegear.vault.ui.commands.CheckOutCommand.work(CheckOutCommand.java:22)
at com.sourcegear.vault.ui.commands.AbstractCommand.run(AbstractCommand.java:89)
at com.sourcegear.vault.ui.commands.AbstractCommand.run(AbstractCommand.java:219)
at com.sg.uihelper.runnable.DeferredProgressMonitorDialogContext$RunnableWithProgressWrapper.run(DeferredProgressMonitorDialogContext.java:173)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

[Beth]

Vault 4.0.6 over all is not supported on Windows 7. Support for Windows 7 is in Vault 5.0.3.

Also, the issue you have was fixed in Vault 5.0.3.