3

I have been trying to set up an Enterprise repository for our company using Archiva. While the installation was quite simple, I am now stuck at issue where the Archiva could not reach out to the Central Repository via our corporate proxy.

I did the following to setup the Proxy (Screen shots below)

  1. Added a Network Proxy via the Apache UI.
  2. Updated the ProxyConnector.
  3. Updated the configuration for Central repository

I still see the Remote Check fails. enter image description here

Any insights?

I did double check the Proxy configuration and also used the same configuration with nexus SonaType and it works fine there.

I also made sure the NetworkProxy is in the archiva.xml file.

Updated: 06/16/2015

I updated the configuration to use https://repo.maven.apache.org/maven2 and also tried to use https and https for our network proxy.

Another thing I've noticed is that the Proxy Connector settings show "Network proxy : None" even though it is configured. (screen shots below)

enter image description here

enter image description here

f_puras
  • 2,521
  • 4
  • 33
  • 38
Harish
  • 133
  • 1
  • 10
  • Did you resolve your issue? I got the same one and keep thinking this must be a bug... – JSamir Feb 26 '16 at 10:45
  • The "Proxy Connector Settings" popup always shows "Network Proxy: None" in Archiva 2.2.1 Release. Try this [link](http://stackoverflow.com/a/39229385/867816) – Gernot Aug 30 '16 at 13:53

4 Answers4

2

Apache Archiva 2.2.1 release IMHO has various bugs/issues regarding the UI. Check /conf/archiva.xml if the settings presented by the UI resemble/match the settings in that config file.

I encountered that the Web-Interface does not show any warnings/errors, but still the config is not updated.

Furthermore the UI shows wrong values for correctly configured settings. The popup "Proxy connector settings" is one example. It will always show "Network Proxy: none", even if one is correctly configured. Vote for the bug --> https://issues.apache.org/jira/browse/MRM-1920

Gernot
  • 1,094
  • 4
  • 25
  • 39
0

ensure you configure network proxy protocol to http or https. You must also use https://repo.maven.apache.org/maven2 (note the https)

Olivier Lamy
  • 2,280
  • 1
  • 14
  • 12
  • Olamy, I've updated the post with the information with the changes I've made with your suggestions. Still no luck yet, Any help is appreciated. – Harish Jun 15 '15 at 15:31
  • Direct connection works for me, but the "Network Proxy" doesn't. Is there any update related to this problem? If not, can we just ignore and go for "Nexus" or "Artifactory"? – bchetty Sep 29 '15 at 13:18
0

I've had the same problem and installed 2.2.1-SNAPSHOT.

Although the visual bug still seems to be there (clicking the button in Proxy Connectors shows Network proxy: none) the proxy is being used and the repository is working fine.

JSamir
  • 1,057
  • 1
  • 10
  • 20
  • Face same issue, can't find a link to download, by any chance do you still have a link? – vadimvolk Apr 28 '16 at 05:23
  • 1
    Yes its kinda tricky, since they sadly link to the stable release of Archiva in the release notes of the snapshot. Needed to find the buildserver, here you go: https://builds.apache.org/view/A-D/view/Archiva/job/archiva-master-build/ – JSamir Apr 28 '16 at 09:48
0

I have managed to have it working by including this XML in the POM:

  <distributionManagement>
    <repository>
        <id>internal</id>
        <url>http://localhost:8080/archiva/repository/internal/</url>
    </repository>
</distributionManagement>

<repositories>
    <repository>
        <id>internal</id>
        <name>Archiva Managed Internal Repository</name>
        <url>http://localhost:8080/archiva/repository/internal</url>
        <releases>
            <enabled>true</enabled>
        </releases>
        <snapshots>
            <enabled>false</enabled>
        </snapshots>
    </repository>
</repositories>
ochavoya
  • 1
  • 1
    Your answer would be ranked better, if you would ad some context add/or explanation, to it. – winner_joiner Apr 25 '16 at 20:05
  • 2
    I don't understand how this can possibly help with proxy issues with the network. Sure you didnt change something else too? – JSamir Apr 28 '16 at 11:10