Resolved Error installing plug-ins - Win10 portable install (Zip)

[Mike Byrnes]

I wanted to share my experience with the plug-in installation error.  Over the last few years a number of people have encountered an error (see attached screen-shot) when attempting to install the two Argunet plug-ins.  All plug-in install errors reported on this forum seem to involve the same files (see screen-shot), with one of two types of errors. The first error is "No repository found" and the other is "Error while reading from repository". 

Sebastian referenced a rather "messy" (think that was the chosen word) manual install in this post: https://groups.google.com/d/msg/argunet-users/DGws4j3AKxk/psIPVWnAAgAJ  instead of the fairly simple fix he recommended in this post https://groups.google.com/d/msg/argunet-users/Wy42xrbzv7I/Zk289e0OBAAJ 

Both errors can be thought of as network based unless the repo's have been deleted.  I installed Argunet today on Win10 as portable using the Zip download and encountered a "No repository" error that prompted one thought process to resolve. I'm not sure why I tried to install again without resolving but when I did I encountered the "reading from repository" error.  In the span of a short time I had both types of error. The path of least resistance was to assume network issue and add the two lines of code as shown below and noted in Sebastian's simple fix post referenced above.

To save some time here is the direct quote from Sebastian:

"Perhaps, this error is due to slow network-connections. Could you please try the following: Find the directory where you installed argunet on your computer. There you should find a file "configuration/config.ini". Open it with a file-editor of your choice and add the following two lines into the file:

    org.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=10000
    org.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=10000

    then save it, restart argunet & retry installing plugins."

This fixed the problem and allowed the plug-in installation and all is good.  Since I encountered both types of error and this fix worked (instead of the messy one), I recommend that anyone with a plug-in installation error try this fix first.

Argunet may want to consider amending the Config.ini file to include these two lines.  I'm not a Java guru and realize their may be a good reason not to do this which is why I say consider. 

Thank you for creating Argunet. It is a brilliant solution.