Apache Archiva 2.2.0 network proxy not working

I am trying to create an Enterprise repository for our company using Archiva. Although the installation was pretty straightforward, I now ran into an issue where Archiva was unable to contact the Central Repository through our corporate proxy.

I did the following to set up a proxy (screenshot below)

  • Added network proxy via Apache interface.
  • Updated ProxyConnector.
  • Updated configuration for central repository

I can still see that the remote access validation is failing. enter image description here

Any ideas?

I double checked the proxy config and also used the same config with Nexus SonaType and it works great there.

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

Updated: 06/16/2015

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

Another thing I noticed is that "Network proxy: None" is displayed in the proxy settings, even though it is configured. (screenshots below)

enter image description here

enter image description here

+3


source to share


4 answers


Apache Archiva 2.2.1 release IMHO has various bugs / issues regarding the user interface. Check /conf/archiva.xml if the options presented in the UI match / match the settings in this config file.

I ran into the web interface not showing any warnings / errors, but the config is not updated.



In addition, the user interface shows incorrect values ​​for correctly configured parameters. The Proxy Socket Settings popup is one example. It will always show "Network Proxy: No" even if configured correctly. Vote on bug -> https://issues.apache.org/jira/browse/MRM-1920

+2


source


make sure you set your network proxy protocol to http or https. You should also use https://repo.maven.apache.org/maven2 (pay attention to https)



0


source


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

Although the visible error is still present (clicking the button in the proxy sockets shows Network proxy: none) the proxy is in use and the repository is working fine.

0


source


I managed to get it to work 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>

      

0


source







All Articles