Bug 195296 - Embedder falls back to IDE's proxy settings
Embedder falls back to IDE's proxy settings
Status: RESOLVED WONTFIX
Product: projects
Classification: Unclassified
Component: Maven
7.0
PC Linux
: P3 (vote)
: TBD
Assigned To: Jesse Glick
issues@projects
:
Depends on: 202703
Blocks: 194916
  Show dependency treegraph
 
Reported: 2011-02-10 15:19 UTC by Jesse Glick
Modified: 2011-09-26 23:36 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2011-02-10 15:19:52 UTC
Even with a valid Maven mirror setup in ~/.m2/settings.xml, which works on the command line, Wireshark confirms that the IDE's online embedder downloads artifacts from the original server, not the mirror.
Comment 1 Jesse Glick 2011-02-10 15:46:26 UTC
Background is bug #195190.
Comment 2 Jesse Glick 2011-02-10 15:47:56 UTC
Bug #194916 is also of interest.
Comment 3 Jesse Glick 2011-08-30 14:54:53 UTC
Seems to be working as expected in a dev build. With settings.xml specifying a local Nexus mirror, downloading dependencies of a project (or sources or Javadoc) makes no internet connection except when populating the Nexus cache.
Comment 4 Jesse Glick 2011-08-30 15:07:52 UTC
Proxy settings also seem to be honored in a dev build. Replaced settings.xml with one which just declared the Oracle proxy and went on VPN. After deleting local artifacts, both command-line Maven build, and Download Declared Dependencies, went through the proxy server.
Comment 5 Jesse Glick 2011-08-30 15:26:14 UTC
However, a different scenario: start the IDE with the system settings set to use a proxy; remove all config from settings.xml; and DDD. That does go through the proxy (and so succeeds). Not sure if this is a bug or a feature.
Comment 6 Jesse Glick 2011-09-26 23:36:31 UTC
Fix of #202703 may have changed things; seems that settings.xml was being ignored for purposes of MavenEmbedder.resolve. Would really be nice to have this kind of thing be part of the test spec for Maven, since it is difficult to set up a sufficiently realistic test environment other than my own, and I have yet to get automated tests to cover Maven network operations.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo