Community
Participate
Working Groups
Created attachment 258378 [details] Error
Hi, thank you for the bug report. Please have a look at the Error Log whether you find more detailed messages regarding your network connectivity there. This would help us diagnose the problem. Also, please share some more information about your network setup: - Are you using some kind of network proxy (if so, with authentication?) - Can you download this file [1] manually, i.e., through a web browser. Best wishes, Andreas [1] <http://download.eclipse.org/recommenders/models/mars/org/eclipse/recommenders/index/0.0.0-SNAPSHOT/index-0.0.0-20150617.073902-1.zip>
*** Bug 483355 has been marked as a duplicate of this bug. ***
*** Bug 478500 has been marked as a duplicate of this bug. ***
*** Bug 483619 has been marked as a duplicate of this bug. ***
*** Bug 470890 has been marked as a duplicate of this bug. ***
*** Bug 469067 has been marked as a duplicate of this bug. ***
Created attachment 259782 [details] Stacktrace copied from the error log
Same error on my pc (behind company firewall, using a proxy). Attached the stacktraces of the error log. Session Data: eclipse.buildId=4.5.1.M20150904-0015 java.version=1.7.0_55 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_AT Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.java.product There are two things worth to add: 1) I am using Java7 and added those lines to the eclipse.ini -Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclient4 -Dorg.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=3000 -Dorg.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=3000 This is a workaround for the problem described in http://stackoverflow.com/questions/17338212/eclipse-kepler-not-connecting-to-internet-via-proxy/33606475#33606475 2) The problem itself seems clear: "Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. ) (407)", but how/where to set the credentials? I setup the Network Connections within the Preferences and I am able to fetch SVN repositories, view the marketplace and fetch / install plugins.
(In reply to Andreas A. from comment #8) > Same error on my pc (behind company firewall, using a proxy). > > Attached the stacktraces of the error log. Thank you. > Session Data: > eclipse.buildId=4.5.1.M20150904-0015 > java.version=1.7.0_55 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_AT > Framework arguments: -product org.eclipse.epp.package.java.product > Command-line arguments: -os win32 -ws win32 -arch x86 -product > org.eclipse.epp.package.java.product > > > There are two things worth to add: > > 1) I am using Java7 and added those lines to the eclipse.ini > -Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf. > provider.filetransfer.httpclient4 > -Dorg.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=3000 > -Dorg.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=3000 I'm afraid those lines won't have an effect on Eclipse Code Recommenders, as it does not use ECF to access the network, but rather Eclipse Aether (which then uses Apache HttpClient 4.x). Is the "excludeContributors" of "httpclient4" required for you to get ECF-based network access to work, e.g., to access update sites? If so, it hints at a problem with Apache HttpClient 4.x, which we unfortunately *indirectly* depend on through Aether. > This is a workaround for the problem described in > http://stackoverflow.com/questions/17338212/eclipse-kepler-not-connecting-to- > internet-via-proxy/33606475#33606475 > > 2) The problem itself seems clear: "Proxy Authentication Required ( The ISA > Server requires authorization to fulfill the request. Access to the Web > Proxy filter is denied. ) (407)", but how/where to set the credentials? > I setup the Network Connections within the Preferences and I am able to > fetch SVN repositories, view the marketplace and fetch / install plugins. Code Recommenders should take your proxy settings (as configured under General > Network Connections) into account and pass that along to Aether. Anyway, there's one other user of Aether in Eclipse: m2e (the Maven integration). AFAIK, they use a different HTTP library under the hood (not HttpClient). If you have m2e installed (it's part of many packages), can you please create a "New > Maven Project" using the "maven-archetype-quickstart". In the "Console" view ("Maven Console"), you should then see something like this: 2/17/16, 9:52:21 AM GMT+1: [INFO] Downloading https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-quickstart/1.1/maven-archetype-quickstart-1.1.jar 2/17/16, 9:52:21 AM GMT+1: [INFO] Downloaded https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-quickstart/1.1/maven-archetype-quickstart-1.1.jar 2/17/16, 9:52:21 AM GMT+1: [INFO] Downloading https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-quickstart/1.1/maven-archetype-quickstart-1.1.pom 2/17/16, 9:52:21 AM GMT+1: [INFO] Downloaded https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-quickstart/1.1/maven-archetype-quickstart-1.1.pom If not, then m2e has also problem working with your proxy. Any error messages it produces would be helpful to us.
Thank you for your fast and detailed response. I'll try to gather the relevant information during the next working days and answer your questions as soon as possible (probably early next week).
(In reply to Andreas A. from comment #10) > Thank you for your fast and detailed response. I'll try to gather the > relevant information during the next working days and answer your questions > as soon as possible (probably early next week). No hurry. That being said, any information you may have about your proxy setup would be valuable to us. What proxy software in what version are you using? What authentication method, if any, does it use (Basic, NTLM, etc.)? Proxy issues are unfortunately extremely hard to diagnose from afar, in particular if commercial proxy software (Microsoft ISA?) is involved, as we can't just put together a test setup.
Hi. I tried as you suggested: (1) Remove the excludeContributors and check connection to marketplace / update-site (2) Remove the excludeContributors and create a new maven project (3) Using the excludeContributors line and create a new maven project Any help is appreciated. In the meantime, I'll gather some more information on our proxy setup. Regards, Andreas (1) I cannot access the update-sites, marketplace, etc. anymore. Dialog: HTTP Proxy Authentication Required: http://download.eclipse.org/releases/mars/compositeContent.xml HTTP Proxy Authentication Required: http://download.eclipse.org/releases/mars/compositeContent.xml Proxy Authentication Required Stacktrace (ErrorLog): org.eclipse.ecf.filetransfer.BrowseFileTransferException: Proxy Authentication Required at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:287) at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) (2) It results in a different error (but indicates the same problem): Could not resolve archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.1 from any of the configured repositories. Could not resolve artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 Could not transfer artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from/to central (https://repo.maven.apache.org/maven2): Connection refused: connect Could not transfer artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from/to central (https://repo.maven.apache.org/maven2): Connection refused: connect org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from/to central (https://repo.maven.apache.org/maven2): Connection refused: connect at io.takari.aether.connector.AetherRepositoryConnector$2.wrap(AetherRepositoryConnector.java:895) at io.takari.aether.connector.AetherRepositoryConnector$2.wrap(AetherRepositoryConnector.java:1) at io.takari.aether.connector.AetherRepositoryConnector$GetTask.flush(AetherRepositoryConnector.java:673) at io.takari.aether.connector.AetherRepositoryConnector.get(AetherRepositoryConnector.java:310) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:753) at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:743) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:720) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype(ProjectConfigurationManager.java:870) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:784) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:760) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:758) at org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard$5.doCreateMavenProjects(MavenProjectWizard.java:243) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectJob$1.doCreateMavenProjects(AbstractCreateMavenProjectJob.java:50) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectJob.runInWorkspace(AbstractCreateMavenProjectJob.java:54) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at com.squareup.okhttp.internal.Platform.connectSocket(Platform.java:107) at com.squareup.okhttp.Connection.connect(Connection.java:156) at com.squareup.okhttp.Connection.connectAndSetOwner(Connection.java:175) at com.squareup.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:120) at com.squareup.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:330) at com.squareup.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:319) at com.squareup.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:241) at com.squareup.okhttp.Call.getResponse(Call.java:271) at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:228) at com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.java:199) at com.squareup.okhttp.Call.execute(Call.java:79) at io.takari.aether.okhttp.OkHttpAetherClient.execute(OkHttpAetherClient.java:154) at io.takari.aether.okhttp.OkHttpAetherClient.get(OkHttpAetherClient.java:100) at io.takari.aether.connector.AetherRepositoryConnector$GetTask.resumableGet(AetherRepositoryConnector.java:600) at io.takari.aether.connector.AetherRepositoryConnector$GetTask.run(AetherRepositoryConnector.java:453) at io.takari.aether.connector.AetherRepositoryConnector.get(AetherRepositoryConnector.java:304) ... 27 more (3) Exclude is now back in the eclipse.ini. It states the following error: Could not resolve archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.1 from any of the configured repositories. Could not resolve artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 Failure to transfer org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from/to central (https://repo.maven.apache.org/maven2): Connection refused: connect Failure to transfer org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from/to central (https://repo.maven.apache.org/maven2): Connection refused: connect org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from/to central (https://repo.maven.apache.org/maven2): Connection refused: connect at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238) at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:753) at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:743) at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:720) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype(ProjectConfigurationManager.java:870) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:784) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:760) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:758) at org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard$5.doCreateMavenProjects(MavenProjectWizard.java:243) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectJob$1.doCreateMavenProjects(AbstractCreateMavenProjectJob.java:50) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectJob.runInWorkspace(AbstractCreateMavenProjectJob.java:54) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
(In reply to Andreas A. from comment #12) > Hi. I tried as you suggested: > (1) Remove the excludeContributors and check connection to marketplace / > update-site > (2) Remove the excludeContributors and create a new maven project > (3) Using the excludeContributors line and create a new maven project > > Any help is appreciated. In the meantime, I'll gather some more information > on our proxy setup. > (3) Exclude is now back in the eclipse.ini. It states the following error: > > Could not resolve archetype > org.apache.maven.archetypes:maven-archetype-quickstart:1.1 from any of the > configured repositories. > Could not resolve artifact > org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 > Failure to transfer > org.apache.maven.archetypes:maven-archetype-quickstart:pom:1.1 from > https://repo.maven.apache.org/maven2 was cached in the local repository, > resolution will not be reattempted until the update interval of central has > elapsed or updates are forced. Oh well, I should have thought of that... :-( Maven caches resolution failures for 24 hours, so this just gives us the error for (2) again, albeit with slightly different wording. Either try things again after 24 hours or, if you want to test this earlier, delete the following folder ~/.m2/repository/org/apache/maven/archetypes before you reattempt scenario (3). Anyway: Thank you very much for your time and effort in testing these scenarios. This really helps.
*** Bug 492288 has been marked as a duplicate of this bug. ***
*** Bug 492579 has been marked as a duplicate of this bug. ***
*** Bug 496052 has been marked as a duplicate of this bug. ***
Comment on attachment 259782 [details] Stacktrace copied from the error log Hi, I am currently migrating our standard eclipse installation from Eclipse Kepler to Eclipse Neon.2 Release (4.6.2). The attached stacktrace (and of course an annoying message box) occurs as soon as the code recommendation feature wants to access something on the internet. I am behind an NTLM-proxy (that already caused some headache), but right now everything else (like the marketplace) seems to work. My Active Provider is set to "Native" and the following Schemes are set: HTTP, HTTPS, FTP, GOPHER Is there any setting to check / change to get it work? Best Regards, Andreas A. ---------------------------- My eclipse.ini looks like this: -startup plugins/org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.401.v20161122-1740 -product org.eclipse.epp.package.java.product --launcher.defaultAction openFile -showsplash org.eclipse.platform -vm C:/Program Files/Java/jdk1.8.0_112/jre/bin/server/jvm.dll --launcher.appendVmargs -vmargs -Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclient4 -Dosgi.requiredJavaVersion=1.8 -XX:+UseG1GC -XX:+UseStringDeduplication -Xms512m -Xmx1024m
Hi (and sorry for the double post. Is it true that there's no edit functionality, or was I to blind to find it?) Last year I tried to do the upgrade from Kepler to Mars, but unfortunately I had to stop the migration. Now there's (some) time left to update so we decided to go for Neon. It seems that I found "my own stacktrace" again via google and "blindly" made a comment on it. So the setup is still the same as above (but in this case using NEON). The eclipse.ini can be found within my previous comment. Are there any things to check (like you suggested using .m2)? Best Regards, Andreas
(In reply to Andreas A. from comment #18) > Hi (and sorry for the double post. Is it true that there's no edit > functionality, or was I to blind to find it?) AFAICT, there's no "Edit" in Bugzilla. > Last year I tried to do the upgrade from Kepler to Mars, but unfortunately I > had to stop the migration. Now there's (some) time left to update so we > decided to go for Neon. > > It seems that I found "my own stacktrace" again via google and "blindly" > made a comment on it. > > So the setup is still the same as above (but in this case using NEON). The > eclipse.ini can be found within my previous comment. AFAIK, there's nothing in the eclipse.ini that you can do to improve things. Code Recommenders is in a bit of a pickle, as we are rather high up the stack: Code Recommenders -> Eclipse Aether -> Apache HttpClient Note that the Marketplace Client does things differently: MPC -> ECF -> Apache HttpClient The system properties you've put into your eclipse.ini configure ECF -- and tell it not to use Apache HttpClient (but that choice is made for us by Eclipse Aether). One approach I can image is inserting ECF into Eclipse Aether as well: Code Recommenders -> Eclipse Aether -> ECF -> Apache HttpClient That way, we can ensure that Code Recommenders behaves like the MPC, as they both share the lower layers. But as Eclipse Aether is unmaintained (they moved back to the Apache Foundation and became a part of Apache Maven again), I don't know whether this is worth the effort, in particular, as we don't have an NTLM setup ourselves to reproduce the problem to begin with.
Hi, thank you for your reply! As far as I understand there are two main problems: - the apache httpclient4 has a bug concerning the usage of an NTLM-Proxy. This issue usually happens within the networks of companies. Excluding httpclient4 allows me to -at least- open the marketplace / install software from third parties. - the code recommenders are using a legacy component that itself has a(nother) bug concerning the usage of an NTLM-Proxy. So for me the biggest problem is that although I am able to define a proxy, my settings are ignored by some components. Temporary solution will be disabling the recommenders feature... Best regards, Andreas
(In reply to Andreas A. from comment #20) > As far as I understand there are two main problems: > - the apache httpclient4 has a bug concerning the usage of an NTLM-Proxy. > This issue usually happens within the networks of companies. Excluding > httpclient4 allows me to -at least- open the marketplace / install software > from third parties. Yes, HttpClient has some known issues with NTLM. Note that the Eclipse IDE currently plans to move to a newer version of HttpClient (4.3.x -> 4.5.x), which *may* fix some issues. I haven't dug through the HttpClient release notes yet to see whether this is the case, though. > - the code recommenders are using a legacy component that itself has > a(nother) bug concerning the usage of an NTLM-Proxy. Note quite: The legacy component (Eclipse Aether) just ties us to Apache HttpClient, which apparently has some issues with NTLM. > So for me the biggest problem is that although I am able to define a proxy, > my settings are ignored by some components. Temporary solution will be > disabling the recommenders feature... Yes, disabling Code Recommenders may be your best option for now. If you are really keen on recommendations for org.eclipse.* types, however, you can download all models and use a file: URI. See [1]. [1] <http://www.eclipse.org/recommenders/download/#cannot-access-update-site>
I was not aware (anymore) of downloading the files manually. Updating the httpclient version sounds great. My problems are solved so far. Thank you for your further explanation and all the effort you (and the other commiters) are putting in this project! Best regards, Andreas
