Eclipse Community Forums: Oomph » Automatic Remote Index Update

Help

Home

Home » Eclipse Projects » Oomph » Automatic Remote Index Update

Show: Today's Messages :: Show Polls :: Message Navigator

Automatic Remote Index Update [message #1754295]

Thu, 16 February 2017 09:08

Malte Brunnlieb

Messages: 27
Registered: February 2011

Junior Member

Hi,

I am facing the issue, that our redirected oomph index seems to not be updated on installer launch.
In detail I am observing the following:

1. I start the oomph installer with a index redirection to our own products and projects and run one installation of product X with project Y once.
2. Afterwards, I close the installer, restart the PC, whatever... and change the project definition in the remote index files.
3. Then I start the installer again and I will get the unchanged project definition, respectively, the first version I previously installed once.
After some trials, I realized, that the index is cached in the home folder in .eclipse or .p2 repository. I am not entirely sure. After deleting both folders, I will get the correct remote index.

So why does this happen? I would expect updating from the remote index should be done on every launch of the installer, right? If not, is there any workaround to do so?

Best Regards,
Malte

Report message to a moderator

Re: Automatic Remote Index Update [message #1754317 is a reply to message #1754295]

Thu, 16 February 2017 11:07

Ed Merks

Messages: 33216
Registered: July 2009

Senior Member

The cache in ~/.eclipse/org.eclipse.oomph.setup/cache includes not just the file but also a corresponding *.etag (generally the ETag the server provides in the response header, or the Last-Modified from the response header, if the header doesn't provide an ETag). The installer initially loads without etag checking (so loads the cache), and then reloads with etag checking. This should generally update the cache, but if the server is providing neither an updated ETag nor an updated Last-Modified for the file being downloaded then the cache will look up-to-date and will be used. Perhaps-Doomph.setup.ecf.trace=true will help show what's going on in your case...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Automatic Remote Index Update [message #1754622 is a reply to message #1754295]

Tue, 21 February 2017 06:54

Malte Brunnlieb

Messages: 27
Registered: February 2011

Junior Member

Thanks. We will check. We are basically pointing the index to an apache2 served directory.
We will check what is not provided, thanks for the property pointer.

Report message to a moderator

Re: Automatic Remote Index Update [message #1754628 is a reply to message #1754622]

Tue, 21 February 2017 07:40

Malte Brunnlieb

Messages: 27
Registered: February 2011

Junior Member

I just checked what is returned in our case. For files the ETag as well as last modified property is correctly returned by the server.
The ETag seems to be a uid.

Report message to a moderator

Re: Automatic Remote Index Update [message #1754644 is a reply to message #1754628]

Tue, 21 February 2017 09:47

Ed Merks

Messages: 33216
Registered: July 2009

Senior Member

And when the file is changed, the server returns a different ETag for it?

In the end, if I'm to fix some problem, I'll need a way to reproduce the problem...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator