Saying that the index is pulled every time eclipse is restarted is
inaccurate.
Code to pull index is trigged on indexer plugin activation.
Indexer plugin activation occurs lazily.
Indexer plugin activation occurs, for example, when pom is about to be
modified.
Indexer plugin updates the index once per eclipse session, by sending a
request with the If-Modified-Since header.
I have repo1.maven.org set to 192.168.1.131 (in /etc/hosts) on all of my
dev machines for the past week (Since Dec 8).
Since I rarely modified the pom on a project this week, i only had 2
requests for the index show up in my Apache httpd logs on my
192.168.1.131 box all week.
I have also started and stopped Eclipse instances with Q4E installed
hundreds of times this week (running Plug-in JUnit tests with full
eclipse workspace startup).
-joakime
Carlos Sanchez wrote:
we are working on it see
http://code.google.com/p/q4e/issues/detail?id=465
the if-modified-since is being used but for some reason everytime
eclipse is restarted it may pull the index again, although only once
per restart, index is not retrieved after that.
On Fri, Dec 12, 2008 at 11:09 AM, Brian E. Fox <[email protected]> wrote:
Part of this problem seems to be how Nginx handles the
If-Modified-Since. It does an exact match and that's all. Fortunately S3
does handle it correctly, so my previous suggestion to use redirects to
S3 for the index would help mitigate these problems. It appears that
Abel is also working on a patch.
From: Brian E. Fox [mailto:[email protected]]
Sent: Friday, December 12, 2008 12:09 PM
To: [email protected]
Cc: Maven Project Management Committee List
Subject: More index troubles (q4e this time)
It came to my attention this morning that Q4e doesn't check the
timestamp on the index or use the api and thus downloads the index on
every restart. Worse than the Artifactory issue where it wasn't known,
this issue was reported back in June:
http://code.google.com/p/q4e/issues/detail?id=465 It goes without saying
that this is not in the best interest of the repository community. We're
looking into ways to minimize the damage and cost from this and I hope
that team takes extra-ordinary measures to fix and distribute an update
as Artifactory did.
--Brian
