Using an archiva repository to proxy to the ZK EE repository

asked 2012-06-06 10:21:40 +0800

avidD
166 ● 2

Hello,
for anyone interested in this topic, I now spent some time on configuring our archiva server to forward artifact requests to the ZK EE maven repository. The advantage of this is that no developer needs to update their Maven settings.xml file.
To do so, I first configured a remote repository on our archiva server:

Identifier ZK EE
Name ZK EE
URL https://maven.zkoss.org/repo/zk/ee
Type Maven 2.x Repository

Then a proxy connector must be configured in archiva:

ZK EE
ZK EE
https://maven.zkoss.org/repo/zk/ee

Settings
Network Proxy: (direct connection)
Policies:
propagate-errors-on-update always
cache-failures no
releases once
propagate-errors stop
snapshots never
checksum fix
White List: "org/zkoss/**"

This, however, was not sufficient as the zk certificate is not signed by a trusted authority. To fix this you must add the certificate to a certificate store:

on the command line: keytool -import -alias zkee -file ZKOSS_root_CA.crt -keystore jssecacerts

This will create a file called jssecacerts in the current directory. This file must be copied to the JAVA_HOME/jre/lib/security folder of the JVM used to run the archiva server. Maybe a restart of the server is necessary now, I didn't try without restart.

That's it, there is no need now anymore to add repositories or passwords to neither settings.xml nor any POMs. Of course, however, you just did the same for the archiva server, but only once and for all.

Cheers,
David