The configuration in the archiva.xml file seems correct. The corpproxy text is in the networkProxy element for the appropriate items. I'll post it when I get back to my desk. On May 21, 2014 1:45 AM, "Olivier Lamy" <[email protected]> wrote:
> Sounds an issue (at least in the ui level to display settings in the > table list but should work when editing the proxy connector ) > Can you create a jira with some screenshots? > Anyway you can still check the configuration in the archiva.xml file. > > > Thanks > Olivier > > On 20 May 2014 08:40, Rick Richardson <[email protected]> wrote: > > First, thank you for making such a great product. It is very > > straightforward and easy to use. I am sure that my network proxy setting > > issues are temporary and quite possibly related to something I've screwed > > up. > > > > I am running 2.0.1 > > > > I have a pretty stock standalone deployment. I am trying to use the > > internal/central repo, + I have created a new repo for clojars. > > > > I have created a new Network Proxy called corpproxy. > > > > I have set corpproxy to be the network proxy for both the Remote > > Repositories as well as in the Proxy Connectors. So that when you edit > the > > settings, corpproxy shows up selected in the dropdown. > > > > However.. when you click on the question-mark button under the Proxy > > Connector Settings button, the Network Proxy shows up as "none" > > > > When I try to fetch an index or just try to use the repo via maven, it > > fails and I get either a No Route To Host (expected, because our internal > > DNS returns a bogus address for everything external) or I get a > connection > > timed out trying to reach repo.maven.org. So it is definitely not > trying > > to go through the proxy in either case. > > > > Thoughts? > > > > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy >
