This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I use NB behind the corporate proxy settings. I have set "Use System Proxy Settings" option and added "-J-Djava.net.useSystemProxies=true". Now, I can use NB's webkit browser, to open any website [not blocked by the firewall, as well as URL of maven repositories]. But. whenever I create a maven project, it fails to download the dependency. Nor does it update the index for Repositories. From the IDE log, I find this, repeating: INFO [org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultHttpClient]: I/O exception (java.net.SocketException) caught when connecting to the target host: Malformed reply from SOCKS server INFO [org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultHttpClient]: Retrying connect But, from the command prompt, maven works just fine, with <proxy> setting in settings.xml Kindly hint me how to fix this issue. Switching back and forth each time, from IDE to command-prompt, is a bit painful.
I think Maven uses its own proxy setting, reassign ... feel free to reassigne
most likely a duplicate of issue 211387, for maven related queries both maven and IDE's settings are used. I believe the workaround is to make sure that SOCKS proxy in IDE's options is not filled in.
Here is one finding from my side. This issue only occurs when I select Maven Home, separate from the bundled installation. e.g. If I have installed maven 3.0.5 in C:\tools\maven-3.0.5 and make that as maven Home in NetBeans, the issue arises for all stuff I mentioned in the bug. Now I have changed Maven Home, to "bundled" option and voila, things work fine. Moreover, my earlier setting of "-J-Djava.net.useSystemProxies=true" costs me failure of server startup [SOCKS exception]. So, I removed that from {netbeans.conf} to get things running once again.
(In reply to comment #3) > Here is one finding from my side. > This issue only occurs when I select Maven Home, separate from the bundled > installation. e.g. If I have installed maven 3.0.5 in C:\tools\maven-3.0.5 and > make that as maven Home in NetBeans, the issue arises for all stuff I mentioned > in the bug. Now I have changed Maven Home, to "bundled" option and voila, > things work fine. most likely unrelated and only masking some other change. All IDE code is using exclusively the maven binaries shipped with the IDE (that's what's on the classpath and is used by all IDE actions that don't trigger a build). The external maven is used exclusively for executing builds. Downloading and processing the maven index is done from the IDE JVM. > > Moreover, my earlier setting of "-J-Djava.net.useSystemProxies=true" costs me > failure of server startup [SOCKS exception]. So, I removed that from > {netbeans.conf} to get things running once again. not sure I follow here..
I believe it's a duplicate of issue 211387 *** This bug has been marked as a duplicate of bug 211387 ***