[MRM-1248] improve documentation about potential issues with the network proxy config...

Merged from: r1073214

git-svn-id: https://svn.apache.org/repos/asf/archiva/branches/archiva-1.3.x@1073222 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/archiva-docs/src/site/apt/adminguide/network-proxies.apt b/archiva-docs/src/site/apt/adminguide/network-proxies.apt
index 320cac109276369ab9ac946d177cc40dadf347c1..72ca9b823bdf903320dbce1266057d5dce111573 100644 (file)
--- a/archiva-docs/src/site/apt/adminguide/network-proxies.apt
+++ b/archiva-docs/src/site/apt/adminguide/network-proxies.apt
@@ -17,5 +17,18 @@ Understanding Network Proxy Configuration of Apache Archiva
   Once configured, the network proxy can be attached to operations that access remote resources. At present, this is configured on the
   remote repository proxy connectors that need to access the remote repository over the HTTP protocol.
 
+* Network Proxy Settings and the JVM
+
+  As Archiva still targets Java 5 and uses the built-in networking libraries, it must configure these settings using
+  system properties. This can be problematic in two scenarios:
+
+    * if you use multiple different network proxies on different proxy connectors, they may clash
+
+    * if you deploy other applications into the same container as Archiva, they will likely pick up the settings
+
+    []
+
+  Please refer to {{{http://jira.codehaus.org/browse/MRM-1248} MRM-1248}} for workarounds and to track the issue.
+
   ~~TODO: walkthrough configuration