|
|
Re: Install requirements on startup "Always" not working [message #1799288 is a reply to message #1799272] |
Tue, 04 December 2018 06:31 |
Ed Merks Messages: 33216 Registered: July 2009 |
Senior Member |
|
|
Version ranges on the p2 director task's requirements is the way to force an update on startup. The way this works is that org.eclipse.oomph.setup.p2.impl.P2TaskImpl.isNeeded(SetupTaskContext), for startup trigger, compares the task's requirements against what is currently actually already installed. So not only must the required unit be present (if not optional ), it must lie within the version range of the requirement; note that as a version range 0.0.0 is all inclusive, i.e., all versions are within this range. If the current installation already satisfies the requirements, the p2 task is not needed.
There is no other proper way to force a full update on startup. The cost of actually checking the repositories for updates is very high. It involves not only loading all the repositories, which is in and of itself expensive, but also involves computing a prerequisite plan to see if there are any actual updates for the requirements relative to what's actually already installed, which is also expensive.
Note that our product catalogs are generated, so the "latest" and "latest.released" have version ranges that change over time (and also the repositories change over time) to force updates on startup. Changing the range (the setup) is the only way to force an update...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04251 seconds