gasilbt.blogg.se

1. #Tortoisehg workbench link project to repository full#
2. #Tortoisehg workbench link project to repository code#

Problems occurred when invoking code from plug-in: "".

#Tortoisehg workbench link project to repository full#

Here is the full error output:īootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_USįramework arguments: -product .cpp.productĬommand-line arguments: -os win32 -ws win32 -arch x86_64 -product .cpp.product If, however, you're using version: 1.9.0.v201110131552, you can bring up Team->Share and select Mercurial, but up on hitting Next, you get the null argument error dialog. Please choose which repository should be connected with the projectĬlicking through configured everything properly. In In *v1.8.2* if and then bring up the context menu on the project and select Team->Share, you can select Mercurial, click Next, and then you're presented with the following dialog:Ĭonnect to an existing Mercurial RepositoryĪn existing Mercurial repository was found in the parent directory. If you import a project that is already configured with Mercurial, but not at root level of the repository things go haywire. I have noticed this same issue on multiple machines running TortoiseHG 2.2, so it has nothing to do with the version of TortoiseHg. MercurialEclipse plug-in fails to import an existing local Mercurial repository