Updater cannot work through proxy

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run the EC on the computer which can connect to Internet only through a 
proxy server.

What is the expected output? What do you see instead?
I expect it to check for updates normally. Instead it fails.

What version of the product are you using? On what operating system?
Java 1.6.22, Windows XP, EC 0023

Please provide any additional information below.
Simple solution to this problem is described here: 
http://stackoverflow.com/questions/376101/setting-jvm-jre-to-use-windows-proxy-a
utomatically

Original issue reported on code.google.com by sergey...@gmail.com on 16 Dec 2010 at 3:10

[GoogleCodeExporter]

What happens when it fails?  Does it say something like "Cannot connect to the 
Internet?"

Thanks for the stackoverflow link.  Would you mind testing this once the issue 
is resolved?  I don't have a lot of experience using proxies myself.  The 
easiest way would probably be to email you a version of the application that 
contains these changes.  I should be able to implement the fix described on 
stackoverflow this weekend.

Original comment by mike.angstadt on 18 Dec 2010 at 3:32

• Changed state: Accepted

[GoogleCodeExporter]

It says: "Update check failed. Please check your internet connection".

I can check the solution for you if you send me the jar.

Original comment by sergey...@gmail.com on 19 Dec 2010 at 6:35

[GoogleCodeExporter]

Email sent.  Thanks.

Original comment by mike.angstadt on 19 Dec 2010 at 4:07

[GoogleCodeExporter]

The fix worked flawlessly.
Thanks for fixing it.

Original comment by sergey...@gmail.com on 20 Dec 2010 at 7:59

[GoogleCodeExporter]

Thanks for testing it. :) Fixed in r248.

Original comment by mike.angstadt on 21 Dec 2010 at 12:32

• Changed state: Fixed

[GoogleCodeExporter]

I'm also behind a proxy, but I'm not sure the latest version 25 is working for 
me. It does tell me there are updates and asks me if I want to update, but it 
seems to do that repeatedly without updating. Unless there are several updates 
that have been released along side the latest version, I'm not sure this is 
working for me. Please advise.

Original comment by jlamar...@gmail.com on 27 Jan 2011 at 4:13

[GoogleCodeExporter]

Everything is working fine for you.
The behaviour you are describing is a known bug in the latest release.
This was reported and fixed as issue #191.
Issue #192 was created in order to raise awarness of the problem and speed up a 
bugfix release.

The issue is trivial (updates do work correctly). The root of the problem is a 
wrong version number stored in the application so it thinks that version v0025 
is newer than the version you are running (which also is v0025). You can 
confirm this by double clicking the 0025.jar file. You will be prompted to 
update - refuse to do it. The application will launch. The title bar will state 
that you are running v0024 which is not true - your version *is* the v0025 
version.

Original comment by netpr...@gmail.com on 27 Jan 2011 at 6:20

[GoogleCodeExporter]

A new JAR has been released with the proper version.  Everything should work 
fine now.

Original comment by mike.angstadt on 27 Jan 2011 at 11:16