commons-httpclient-3.0_rc3 fails during testing phase of upgrade. commons-httpclient-3.0_rc1 builds fine. I looked upstream for bugs but can't find any so i'm wondering if this is a gentoo related problem? it builds fine and fails during testing phase with: testAbsoluteURLOverridesClientDefaultHost(org.apache.commons.httpclient.TestHostConfiguration)java.net.ConnectException: Connection refused it appears to be trying to contact "somewere.outthere.in.pampa" for which the server never responds. I assume this address should possibly be overridden during configuration with something sane but never is? Reproducible: Always Steps to Reproduce: 1. 2. 3.
My initial impression is that this particular test should be disabled if it is going to be trying to make a network connection to a remote host at merge time.
its been two months now and there has been no change to this ebuild to address this bug... perhaps i'm the only one using it?? overriding the address its trying to connect to or disabling this test during merge both seem like sensible solutions to me. both of which are easy fixes...
(In reply to comment #2) > its been two months now and there has been no change to this ebuild to address > this bug... perhaps i'm the only one using it?? First, not everyone runs unit tests via the junit USE flag. Second, the amount of time to resolve a bug isn't exactly depending on the number of people using the package... > overriding the address its trying to connect to or disabling this test during > merge both seem like sensible solutions to me. It would have to be changed to some other host, but the problem is that builds should be able to performed offline without a network connection. So, either we disable any tests which try to make a network connection somehow, or disable all tests. > both of which are easy fixes... The Java team has been severly understaffed for some time. Any patches you can submit to resolve this would be greatly appreciated.
This bug also affects rc4. Many programs depend on >3.0 of commons-httpclient. I realize that the java team is very understaffed, But this is a major bug, blocking many programs. And this bug report has been open since 10/3/2005 which is more than two months. -Joey
This can be gotten arround by adding -junit as that will disable the tests
I just added 3.0 final to portage, and it doesn't seem to be effected by this bug. Please open a new bug if you experience any problems with the new release. As always, thanks for reporting.
