My server has 2 ip, one inner and one outer, we just don't want the
people not in our company to access the archiva, so we want to bind
the archiva to the inner ip. It really confused me for one day, I
tried to search the answer in google, but nothing can help, I just
find out jetty it self can do
Yeah, improvements to the caching should certainly be filed as a
feature request - and we should run through the plan on the dev@ list
if possible.
As far s your original freezing problem goes - I assigned it to the
1.0.1 version yesterday. I've seen another report too and they are
helping to diag
"Cache failure" option is supposed (AFAIK) to enable such caching, and avoid
requesting again and again the same repository, where 404 or timeout occurs.
Reading the code, (DefaultRepositoryProxyConnectors) seems the cache is not
used before requesting a proxyConnector for an artifact. 404 also ar
"mvn eclipse:clean eclipse:eclipse" has just finished
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 134 minutes 34 seconds
[INFO] Finished at: Thu Dec 20 18:14:35 CET 2007
[INFO] Final Memory: 66M/254M
134 minutes to
Hello,
Today, archiva was (again freezed) but restart didn't solve the problem.
Looking in the logs, I saw that one of our remote repositories was dead;
removing it solved the problem.
Archiva do not cache information about unavailable site to not calling
it for each artifact ?
Could be a use
