| Summary: | [Net] Any attempt to connect to CVS server fails with NullPointerException when network proxy is enabled | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Brown <michael> | ||||
| Component: | Team | Assignee: | Platform Team Inbox <platform-team-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | michael, pawel.pogorzelski1, wojciech.galanciak | ||||
| Version: | 3.5.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Michael Brown
Created attachment 150280 [details]
Error with stack trace from Eclipse error log
Michael, it's Eclipse 3.6.0, right? (In reply to comment #2) > Michael, it's Eclipse 3.6.0, right? Hi Pawel, no, is's Eclipse 3.5.1. This bug is referred to here: http://stackoverflow.com/questions/655045/eclipse-still-using-http-proxyhost-settings-when-no-longer-set where a workaround for the bug is also given. Why has this bug been apparently ignored? Hi Michael, Could you provide your CVS connection string (e.g. :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse) or if you cannot do that, at least its modified version (e.g. :pserver:user:password@xxx.yyy.org:/cvsroot/eclipse)? Can you still reproduce this issue in Eclipse 3.6? Hi Wojciech, My CVS connection string is (was): :pserver:tt0504@investserv_old:2401/cvs where investserv_old is a host on the company LAN. I'm unable to say whether the problem is reproducible in Eclipse 3.6 as I'm no longer working at the company where I encountered the problem, and where I am currently there is no network proxy and we're not using CVS. Michael, Thank you for your answer. It looks like you problem was a duplicate of bug 323114. Wojciech, It does appear do be a duplicate of 323114. I will check with my colleagues at my old place of work to see if using a different CVS host name with no underscore resolves the problem. *** This bug has been marked as a duplicate of bug 323114 *** |